-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI Elements for linked announcements and events #98
Comments
No need to include the database part as that is already existing and implemented, but it just wasn't fully working, which it will be soon. |
So I was thinking about this, what do we consider "linked" announcements? Just specific/recur type that have the event's ID? Or would color count too if it matches? and if so, then does universal count as linked too? Just trying to figure out what we should consider linked so that I can work on implementing the backend handling of this to make the SQL query simpler than just getting all announcements and looping through for matching values. |
My thoughts: Also, what about the inverse? |
Unless the event is a Linking |
I think the message is good, makes sure it's clear. |
Should disabled announcements count as being linked? Say, a specific type announcement that is set to disabled. It exists, but it won't be posted... Or should the front-end UI just indicate if its disabled? |
I think maybe a message saying:
And then list the announcement IDs. I think this would fill the dual purposes of letting the user know they exist, but without cluttering/confusing things with the inactive events being displayed. Also going back to the |
Have announcements linked to an event deleted when !e delete xx is used. Additionally, have any linked announcements displayed when !e view XX is used.
The text was updated successfully, but these errors were encountered: