[Schedule] Add custom events
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start by locating the existing room-booking frontend and the schedule entry points that handle timeslot selection. Review how schedule data is stored, then define the event flow for creating, editing, deleting, and confirming removal. Done means custom events can be managed from the schedule and persist in the chosen storage.
Written by the indexing model from the issue text.
Description
Describe the feature
"Edit" Switch
On the main page, add the "edit" switch that is generally turned off. Upon clicking the "edit" switch it will turn on, and it will become possible to add events on specific timeslots similarly to room booking.
Adding events
When a timeslot is selected, an event details window pops up, for which you may enter the event name, room, other people, notes about the event, and so on. Then you can click "Save", and the event will appear in the schedule.
Editing and removing events
You may also click the event, and the window with "edit" and "delete" buttons will show up. Clicking "edit" button prompts an event details window, clicking "delete" button prompts an "Are you sure that you want to delete this event?" window asking for event removal confirmation.
Suggested solution
We could try to take the room booking frontend for selecting the timeslots and store the events in a local user storage (or InNoHassle storage). I cannot provide any purely technical solutions for the feature.
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 25
- Forks
- 12
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 3
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 one-zero-eight/website
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
one-zero-eight/website#432 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
one-zero-eight/website#434 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
one-zero-eight/website#433 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
one-zero-eight/website#429 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 68/100
one-zero-eight/website#428 ·
All issues in one-zero-eight/website
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·