Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(chore): update developer documentation #25

Merged
merged 5 commits into from
Feb 12, 2025
Merged

Conversation

Jipperism
Copy link
Collaborator

@Jipperism Jipperism commented Dec 14, 2024

  • Updates developer documentation for contributing to the sdk.
  • Updates developer documentation for consuming the SDK.
  • Removes redundant references to env vars.
  • Removes redundant references to outdated package manager yarn.
  • Updates typedoc version and configuration to include handwritten guides in the generated docs.
  • Removes outdated github templates.
  • Updates JSDoc annotations.
  • Bump version number.

@Jipperism Jipperism self-assigned this Dec 14, 2024
@Jipperism Jipperism force-pushed the feature/developer-docs branch 4 times, most recently from b1c8fa0 to aff056d Compare December 14, 2024 17:48
.vscode/settings.json Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
doc/_media/cancelOrders.md Outdated Show resolved Hide resolved
@Jipperism Jipperism force-pushed the feature/developer-docs branch 20 times, most recently from f37c9fe to c75bfff Compare December 19, 2024 13:44
Copy link
Member

@pheuberger pheuberger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you're not only removing old code, but also bumping the version number and changing some magic number. I would advocate for even more granular commits, because I don't know why you're doing any of that (except the version bump).

Copy link
Member

@pheuberger pheuberger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great stuff. Thank you so much for making this! It's mostly just nits and a couple of clarifying questions from my side. Being new to the project, I have big gaps in my knowledge and understanding which shows in my questions. Feel free to not elaborate on some of them if you think they're just too preposterous to cover hehe.

Please also don't be put off by the amount of comments. I was very thorough and highlighted very minor things. Generally this is great!

src/utils/api.ts Outdated Show resolved Hide resolved
src/utils/api.ts Outdated Show resolved Hide resolved
.gitignore Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
guides/orderValidity.md Outdated Show resolved Hide resolved
src/HypercertExchangeClient.ts Show resolved Hide resolved
src/HypercertExchangeClient.ts Outdated Show resolved Hide resolved
src/utils/api.ts Outdated Show resolved Hide resolved
typedoc.json Outdated Show resolved Hide resolved
@Jipperism Jipperism force-pushed the feature/developer-docs branch from c75bfff to cbc28cc Compare December 26, 2024 14:08
@Jipperism
Copy link
Collaborator Author

@pheuberger Had a look at all the comments and implemented the feedback. Please close all conversations on the PR that you consider resolved.

Looks like you're not only removing old code, but also bumping the version number and changing some magic number. I would advocate for even more granular commits, because I don't know why you're doing any of that (except the version bump).

I updated the git commit description for fe6ed4b, hopefully that makes things clearer. I think splitting this up in more granular commits would also entail purposely releasing broken versions to NPM, as each commit would require a version bump (otherwise we have version on github that don't exist on NPM)? I can see both sides of the story but maybe that's not necessary for now, let me know what you think.

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
guides/cancelOrders.md Show resolved Hide resolved
typedoc.json Outdated Show resolved Hide resolved
@pheuberger
Copy link
Member

pheuberger commented Jan 3, 2025

@pheuberger Had a look at all the comments and implemented the feedback. Please close all conversations on the PR that you consider resolved.

Looks like you're not only removing old code, but also bumping the version number and changing some magic number. I would advocate for even more granular commits, because I don't know why you're doing any of that (except the version bump).

I updated the git commit description for fe6ed4b, hopefully that makes things clearer. I think splitting this up in more granular commits would also entail purposely releasing broken versions to NPM, as each commit would require a version bump (otherwise we have version on github that don't exist on NPM)? I can see both sides of the story but maybe that's not necessary for now, let me know what you think.

Thank you, @Jipperism! I closed all the conversations that are implemented/answered :)

Can you explain why we would need to release broken versions to NPM? Not every commit needs to be a release, nor have a version bump, unless I'm missing something?

README.md Outdated Show resolved Hide resolved
LICENSE.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
guides/cancelOrders.md Outdated Show resolved Hide resolved
const order = await hypercertExchangeClient.createFractionalSaleMakerAsk({
startTime: Date.now() / 1000, // Use it to create an order that will be valid in the future (Optional, Default to now)
endTime: Date.now() / 1000 + 60 * 60, // If you use a timestamp in ms, the function will revert (this order will be valid for one hour)
price: '10', // Note that this is the price per hypercert unit in wei
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's also documentation on this on the specific strategy contract. It might be good to explain here what the strategy does

guides/executeTrade.md Outdated Show resolved Hide resolved
src/HypercertExchangeClient.ts Show resolved Hide resolved
src/HypercertExchangeClient.ts Show resolved Hide resolved
src/utils/api.ts Outdated Show resolved Hide resolved
@Jipperism Jipperism force-pushed the feature/developer-docs branch 2 times, most recently from b42a8b8 to 832b15b Compare February 6, 2025 13:49
@Jipperism Jipperism force-pushed the feature/developer-docs branch 2 times, most recently from 363f313 to a4c2d96 Compare February 6, 2025 14:05
README.md Show resolved Hide resolved
guides/cancelOrders.md Outdated Show resolved Hide resolved
src/HypercertExchangeClient.ts Show resolved Hide resolved
src/utils/calls/nonces.ts Show resolved Hide resolved
guides/faq.md Outdated Show resolved Hide resolved
guides/faq.md Outdated Show resolved Hide resolved
guides/faq.md Outdated Show resolved Hide resolved
guides/createMakerAsk.md Outdated Show resolved Hide resolved
guides/createFractionalSaleMakerAsk.md Outdated Show resolved Hide resolved
guides/createDirectFractionsSaleMakerAsk.md Outdated Show resolved Hide resolved
@Jipperism Jipperism force-pushed the feature/developer-docs branch 2 times, most recently from f5ceb97 to f72ab83 Compare February 6, 2025 15:10
@bitbeckers
Copy link
Collaborator

As you've release 0.4.0 that'd also need to be merged in here since this PR also influences business logic

@Jipperism Jipperism force-pushed the feature/developer-docs branch 2 times, most recently from 8656be9 to b0eb32e Compare February 10, 2025 15:50
@Jipperism Jipperism mentioned this pull request Feb 11, 2025
@Jipperism Jipperism force-pushed the feature/developer-docs branch from b0eb32e to b702a1a Compare February 11, 2025 19:37
@Jipperism
Copy link
Collaborator Author

Jipperism commented Feb 11, 2025

@bitbeckers has been updated to incorporate changes from 0.4.0

Updates outdated strategy IDs. As we aren't using
hypercertFractionAllowlist strategy currently, it wasn't noticed that
it's outdated. This fixes that already for when we decide to start using
it.

Removes outdated code that's related to:
- Batch transfers
- Subset nonces
- Remove amounts argument when creating a makerask, as in the case of
hypercerts it will always be an array of 1's.
- Bump version number
Updates developer documentation for contributing to the sdk.
Updates developer documentation for consuming the SDK.
Removes redundant references to env vars.
Removes redundant references to outdated package manager yarn.
Updates typedoc version and configuration to include handwritten guides
in the generated docs.
Removes outdated github templates.
Updates JSDoc annotations.
@Jipperism Jipperism force-pushed the feature/developer-docs branch from b702a1a to 853c46f Compare February 11, 2025 19:39
@Jipperism Jipperism merged commit 5b36795 into main Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants