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.
Fix Last Activity Calculation per Repository Item
What does this PR do?
Closes #440
This pull request fixes how the “Last Activity” time is calculated and displayed for each repository item.
Previously, the relative time logic was defined inside the component, which could lead to incorrect or inconsistent behavior across repository items.
This change ensures that each repository correctly computes and displays its own relative last-modified time.
Why is this change needed?
dayjs.extend(relativeTime)should be initialized once, not on every render.What was changed?
dayjs.extend(relativeTime)to module scope.useLastModifiedinto a proper custom hook.lastModifiedupdates correctly whenrepository.last_modifiedchanges.Example
All repository items now correctly display their respective relative last activity times such as:
based on their individual
last_modifiedvalues.Technical Notes
Checklist