Events stored in the database instead of YAML files - first draft - #487
Open
kcomandich wants to merge 13 commits into
Open
Events stored in the database instead of YAML files - first draft#487kcomandich wants to merge 13 commits into
kcomandich wants to merge 13 commits into
Conversation
mcgain
reviewed
Jul 7, 2026
mcgain
reviewed
Jul 7, 2026
kcomandich
commented
Jul 7, 2026
mcgain
reviewed
Jul 7, 2026
mcgain
reviewed
Jul 7, 2026
mcgain
reviewed
Jul 7, 2026
kcomandich
force-pushed
the
feature/events_architecture
branch
4 times, most recently
from
July 8, 2026 02:52
c8b6c90 to
0b8ef91
Compare
mcgain
reviewed
Jul 8, 2026
mcgain
left a comment
Contributor
There was a problem hiding this comment.
Bunch of nit-picking sorry, but they are worth addressing
mcgain
reviewed
Jul 8, 2026
kcomandich
force-pushed
the
feature/events_architecture
branch
5 times, most recently
from
July 21, 2026 02:42
1e2f75e to
2360201
Compare
kcomandich
marked this pull request as ready for review
July 21, 2026 03:11
kcomandich
force-pushed
the
feature/events_architecture
branch
3 times, most recently
from
August 4, 2026 05:05
800ec75 to
50eb16d
Compare
…n Melbourne::Events
Add 'Edit' and 'Delete' buttons to database_events/show Add 'Add New' button to database_events/index
…event_presenter The times used to be hardcoded into the view, now they are in the database so they need formatting
… user is meetup_admin
…being hardcoded in the presenter
leesheppard
force-pushed
the
feature/events_architecture
branch
from
August 4, 2026 06:29
50eb16d to
db5f7c4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move events from a YAML file to the database, and provide a way to create/edit/delete events
There are a few remaining items to finish before it's ready to use, but I wanted to make sure I'm on the right track.
See discussion on #342. Implementation so far:
Note that UUIDs from the events.yml file don't appear to be used, LMK if they should be.
Still to do/fix:
Thanks to @mcgain for advising! 🙏 🎉
Screenshots:
Clone of the Melbourne event/show page, using events table, with Edit and Delete buttons:
New/Edit Event form:
Clone of the Melbourne events page, using events table, with New button:
Clone of the Melbourne home page, using events table: