RealDevSquad / RealDevSquad/website-backend
[RFC] Different timestamp formats used in various collections within our repository
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
We have observed that different timestamp formats (Firestore Timestamp, Unix Timestamp, Epoch Timestamp) are being used inconsistently across collections in our repository. This inconsistency can lead to confusion and complexity when working with timestamps. To ensure consistency and simplify data management, we propose standardizing the timestamp format across all collections.
Proposed Solution:
- Identify all collections that use different timestamp formats.
- Determine the most appropriate timestamp format to use universally across collections (e.g., Firestore Timestamp, Unix Timestamp, ISO 8601).
- Migrate the collections to use the chosen timestamp format consistently.
- Update relevant code and queries to handle the new timestamp format.
- Test and verify the changes to ensure proper functionality.
- Document the standardized timestamp format and update relevant documentation.
- By standardizing the timestamp format, we can improve maintainability, reduce potential errors, and enhance the overall consistency of our repository.
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 inventorying the repository's collections and identifying where Firestore, Unix, and epoch timestamps are used. Decide on the universal timestamp format, then assess the required collection migrations, code and query updates, tests, and documentation changes. Done means all collections and related behavior use the chosen format consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100