Invalid time since creation/update in resource metadata display
- Dominant language
- Scala
- Stars
- 301
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
A resource's "Created at" and "Updated at" is formatted in a user-friendly (difference between current datetime and the datetime of the event + months/day/hour/min conversion) way. I think this is just a particular value of this difference that leads to a not-so-great display but it shows "0 months".
**What part of Nexus is affected**
- [x] Fusion
- [ ] Delta
- [ ] CLI
- [ ] Documentation
**To Reproduce**
Steps to reproduce the behavior, e.g. for Fusion:
(This may not be visible by the time of reproduction)
1. Go to https://bbp.epfl.ch/nexus/web/bbp/mmb-point-neuron-framework-model/resources/https%3A%2F%2Fbbp.epfl.ch%2Fdata%2Fbbp%2Fmmb-point-neuron-framework-model%2F367bc36a-d253-47ab-8bb4-af631895758b
For information this was noticed on April 4th, 2024 and the creation date is March 5th, 2024.
So it is at the limit between displaying in days, and displaying in months.
**Screenshots**
Contributor guide
Research direction
The issue concerns Fusion's resource metadata display for the “Created at” and “Updated at” values, but it names no file, test, or entry point. Start by reproducing the March 5 to April 4 boundary case in Fusion and trace the relative-time formatting; done means the boundary no longer displays an invalid “0 months” value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100