feat: show updated time in asset list#40
Open
luo1324574369 wants to merge 7 commits intonicejade:mainfrom
Open
feat: show updated time in asset list#40luo1324574369 wants to merge 7 commits intonicejade:mainfrom
luo1324574369 wants to merge 7 commits intonicejade:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updatedcolumn to the asset list on the homepageupdatedtocreatedtodatetimeWhy
The asset list previously showed type, amount, and currency, but it did not tell users when a row was last changed. That made it harder to answer basic questions such as:
This change solves that with a low-risk frontend-only update. The backend already returns the necessary time fields, so adding the column in the UI avoids API churn and keeps the scope minimal.
Implementation Notes
client/src/components/ChartWidget/TableWidget.svelteupdatedcreateddatetimecreated/updatedsafelyVerification
cd client && npm run buildBuild completed successfully. Existing repo warnings from Svelte/Tailwind remain, but this change does not introduce a new build failure.