Fix datetime fields
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- database
Research direction
The issue only identifies inconsistent release date values and does not name a file, test, or expected format. Start by locating the database entries containing the release date field and compare the repository's existing conventions. Done means the affected entries use one agreed datetime representation consistently.
Written by the indexing model from the issue text.
Description
The release date field is a bit inconsistent, with some entries having a UNIX timestamp and some other MM-DD-YYYY
- Dominant language
- C
- Stars
- 95
- Forks
- 52
- Avg merge
- 7h 33m
- Merged PRs (30d)
- 1
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.
More from gbdev/database
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
-
database
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
-
GBDK Gallery Opensource
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Hardware features Openschema
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
internal.h中，漏掉了1个定义。 Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#120011 ·