-
Notifications
You must be signed in to change notification settings - Fork 0
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
ACUS: Put hotel booking code, booking link, booking last date in settings #159
Labels
Comments
evoskamp
added a commit
that referenced
this issue
Jan 21, 2024
Try and bring ACNW and ACUS together through: 1. Configuration values 2. Added configuration settings: Copyright holder in footer - config.copyright (string) Used to set range on min and max player in creating games - config.playerMin (positive integer) - config.playerMax (positive integer) - config.minPlayersFloor (positive integer) - config.minPlayersCeiling (positive integer) - config.maxPlayersFloor (positive integer) - config.maxPlayersCeiling (positive integer) Used by ACUS on its hotel page to allow people to book in its block of rooms: - config.hotelBookingCode (string) - config.hotelBookingUrl (string) - config.hotelBookingLastdate (date) Resolves: #155, #158, #160, #161 See also: #159
evoskamp
added a commit
that referenced
this issue
Jan 21, 2024
Instead of sticking configuration.abbr in local variables of acnw and acus, which are essentially inverted Boolean flags, check against its values of 'acus' or 'acnw' directly. It's simpler, clearer, and allows for adding a third (even if only synthetic) site. Resolves: #155, #158, #160, #161 See also: #159
Still need to update the actual hotel page to use them. |
It also would be nice to segment the configuration settings by role, e.g. allow Liz prices, Joe hotel settings, Kit game min/max and such settings. |
evoskamp
added a commit
that referenced
this issue
Jan 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: