-
Notifications
You must be signed in to change notification settings - Fork 221
Open
Labels
Backendgood first issueGood for newcomersGood for newcomersonlydust-waveContribute to awesome OSS repos during OnlyDust's open source weekContribute to awesome OSS repos during OnlyDust's open source week
Description
Guideline
- Carefully read the issue description before applying to ensure you have all the necessary information to start working on it.
- Write a brief description of how you will approach the task (without using ChatGPT).
- Add your Telegram handler in your application (e.g., in OnlyDust or similar)
- Write ETA in your application
What should I do if I have a problem
- Try to google it before asking. Googling is taking major part of dev work
- If you couldn't find answer your question with Google, text your question to dev group with your question.
- Do not send DM to maintainer, it would be better and faster to ask other contributors in chat
How to prepare PR
- Check if your code smell good
- Add
close #<issue number>to link your issue with your PR - Do not commit changes that are unrelated to your task
- Check after you created PR, if you committed everything
Task Description
- In the admin endpoints, add an endpoint called
/assets. Call theAssets statisticmethod from this issue to retrieve the data. Format the response using pydantic BaseModel. - Add integration tests for it.
- Ensure that all tests(workflows) and endpoint works properly.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Backendgood first issueGood for newcomersGood for newcomersonlydust-waveContribute to awesome OSS repos during OnlyDust's open source weekContribute to awesome OSS repos during OnlyDust's open source week