-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[DRAFT] statement-store: re-defining RPC API surface #10452
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
Draft
alexggh
wants to merge
27
commits into
master
Choose a base branch
from
alexggh/api-consolidation
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 15 commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
853a9df
Extend submission result types
AndreiEres c6d8e87
Remove NetworkPriority (which was never used)
AndreiEres 1cc5ae9
Add Invalid result
AndreiEres 550d9fa
Handle encoding_too_large
AndreiEres b153d0f
Add rejected variant
AndreiEres 32b198b
Update from github-actions[bot] running command 'prdoc --audience nod…
github-actions[bot] 31a606b
Update
AndreiEres bc77940
Update
AndreiEres 67d915f
Update PR doc
AndreiEres 068364a
Fix PR doc
AndreiEres 4b6cc03
Update substrate/client/rpc-api/src/statement/mod.rs
AndreiEres 89c3c37
Fix assertion
AndreiEres a3a0a90
Don't copy types
AndreiEres 534ec44
statement-store: api changes
alexggh b3d1b36
Merge remote-tracking branch 'origin/AndreiEres/sss-rpc-types' into o…
alexggh 6ef12d3
Merge remote-tracking branch 'origin/master' into alexggh/api-consoli…
alexggh af1be1d
remove replacement_preference_mask
alexggh c394914
remove unused
alexggh 3ad1478
remove unused
alexggh 31d3f53
remove unused
alexggh 03fcc46
Merge remote-tracking branch 'origin/master' into alexggh/api-consoli…
alexggh acf0103
address feedback
alexggh 65cd2ec
fixup documentation
alexggh e97cb8f
fix documentation
alexggh eca03c7
remove non-api changes for now
alexggh f43fc81
fix typos
alexggh 849c17f
remove original api
alexggh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| title: 'statement-store: New RPC result types' | ||
| doc: | ||
| - audience: Node Dev | ||
| description: |- | ||
| Moved submission failures from JSON-RPC errors into structured result types: | ||
| - Internal submission result type changed to hold more information for clients. | ||
| - The "statement_submit" method now returns enum with clear status variants (New, Known, Invalid, Rejected). | ||
| - NetworkPriority removed as we never used it. | ||
| - Updated and simplified the reputation system. | ||
| - Runtime API wasn't changed. | ||
|
|
||
| crates: | ||
| - name: sc-rpc-api | ||
| bump: major | ||
| - name: sc-rpc | ||
| bump: major | ||
| - name: sc-network-statement | ||
| bump: major | ||
| - name: sc-statement-store | ||
| bump: major | ||
| - name: sp-statement-store | ||
| bump: major |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Just to confirm the logic, am i right that this endpoint immediately provide currently matching statements and then send new matching statement once they appear in the store? Also if the current number of statements is too big will it automatically split them into pages the return in the separate updates?
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.
Yes, the plan is to immediately provide currently matching statements.
Not sure I understand why would you need pagination for the subscribe, you would receive each statement one by one.