Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat: api fungibles pallet #113
feat: api fungibles pallet #113
Changes from 4 commits
360bb2a
e097f80
c8d8b2a
c88387d
224390a
43ae445
bbe01a1
68264da
2481773
c10a8d4
a8c4bb5
4419bad
792fa07
96da2f0
cb54a57
9ec2744
f0fff97
4a476b0
f3cc83a
bd85489
0e49f63
8f6139c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important question: what happens when v1 needed. Is the plan to create a whole new pallet, taking up an index in the runtime, or to just add new functions here?
If the latter, should these functions be prefixed with v0_ to indicate intentions? Whilst renaming wont affect encoding based on call index, it may break integrations using the name obtained via metadata.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is hard to predict but this theoretically doesn't have to change, ever. As long as the standards are being used the api in the contract should never change. If parameter types change slightly, these should be handled in the pallet via a runtime upgrade but this won't require a different version because the type in the contract stays the same.
When a parameter gets added to pallet assets'
transfer
there is a list of things that will happen:transfer
will add some logic via a runtime upgrade.Renaming: makes sure integrations outside of contracts won't break.
Not renaming: makes the code cleaner and there is a high chance we will never need it. If we need it in the end we can change the naming and integrations outside of contracts will break.
v1::fungibles::transfer
where they provide the extra parameter. This function will have a different dispatchable index and will call thev1_transfer()