aave / aave/protocol-subgraphs
consistent symbol naming
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 150
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
Current state of symbol naming:
Subgraph
- mainnet we return aToken.symbol.slice(1) -> e.g.
aUSDC on proto, butaAamUSDC on amm
UI helper contracts
- always return aToken.symbol
We can surely work around that, but it's weird. I'd rather have it consistent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Subgraph symbol handling and the UI helper contract implementations, then compare how each derives the token symbol for mainnet, matic, proto, and amm cases. The issue is done when those paths follow one consistent naming convention and the documented examples produce matching symbols; no specific files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100