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

TODO: Transition from static asset/marketsearch data to nanostore cached data #28

Open
grctest opened this issue Sep 16, 2024 · 0 comments

Comments

@grctest
Copy link
Contributor

grctest commented Sep 16, 2024

It's currently possible that if an user is relying on releases they may miss out on the creation of new assets, as these static JSON dumps are generated at build time.

We should probably move towards having a data system similar to the airdrop tool: https://github.com/BTS-CM/airdrop_tool

On the first launch the user would be prompted with a data fetching modal, it would fetch all the latest data and store it in a persistent nanostore.

This could then be manually triggered by the user, fetching the latest data to avoid missing out on functionality.

With that said, this isn't an issue for all existing assets on the bitshares blockchain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant