bitshares / bitshares/bitshares-ui
Part of #2456 - Don't abuse `get_full_accounts` API
- Dominant language
- JavaScript
- Stars
- 520
- Forks
- 575
- Avg merge
- 12h 7m
- Merged PRs (30d)
- 5
Description
Most time when querying for an account, the UI just want to know the account's name and perhaps whether the account is a LTM. In this case, it's better to use `get_objects` API rather than `get_full_accounts` API.
For even better performance, we can add another lighter API to only return the needed data fields, or make a more flexible API so UI can only ask for a subset of data fields.
Contributor guide
Research direction
Start by locating UI account queries that call get_full_accounts and compare their needs with the data returned by get_objects. Determine whether the intended scope is replacing those calls or designing a lighter or field-selecting API. Done should mean the UI requests only the needed account data and the performance impact is verified, but the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100