Carpenteri1 / Carpenteri1/Gridly
Add Clock widget
- Dominant language
- HTML
- Stars
- 1
- Forks
- 0
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 27
Description
# What
- Add Clock widget type.
# Why
- Add Clock widget to show clock in the current area so the user get a solid data.
## Weather widget
- We want to show the local time or in a specific area the user picks.
# Definition of done
### Client
- Add new clock widget
- Select from different types of clocks, digital and analog
- Data will be collected after save
### Backend
- Backend needs to call an api if the card has no time data
- Backend needs to collect data from the database if the card has time data
- Ratelimiter is needed in order to not collect data from our weather API all the time
- Time data should be stored in a seperate table
- Time data Is stored by location
- If Time data already excites by location, we dont need to collect it again, just link it to the card
- Add new endpoint for widget
- Add new repository for widget
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by mapping the existing weather widget's client, backend endpoint, repository, database, and rate-limiting flow. Done means supporting local or selected-area time, digital and analog clock choices, stored location data, reuse of existing data, and the requested new widget endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, database, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100