We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In order to support search functionality and filters like sort, category, stage and author on the proposal feed we need to index the proposals.
Updating proposals works with snapshots. To simplify the process of indexing instead of updating the database we will work with snapshots as well.
As a starting point use bo's indexer used to indexing devgovgigs posts.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered:
Created this issue to simplify deserializing the contract state with borsh-js near/queryapi#593
Sorry, something went wrong.
Today I created this PR near/near-lake-framework-js#53
Update: I had a call with @ailisp and deployed the latest version of the indexer.
This version succesfully indexed my two proposals but missed the first with index 0 which I'm investigating.
query MyQuery { thomasguntenaar_near_devhub_proposals_delta_proposals { id author_id } thomasguntenaar_near_devhub_proposals_delta_dumps( where: {method_name: {_eq: "set_block_height_callback"}} ) { author method_name block_height proposal_id } }
The latest version is called: devhub_proposals_mining. I integrated it with front end with issue #690
Tguntenaar
No branches or pull requests
In order to support search functionality and filters like sort, category, stage and author on the proposal feed we need to index the proposals.
Updating proposals works with snapshots. To simplify the process of indexing instead of updating the database we will work with snapshots as well.
As a starting point use bo's indexer used to indexing devgovgigs posts.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: