forked from City-of-Helsinki/varaamo
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Release tku-v1.11 #334
Merged
Merged
Release tku-v1.11 #334
Conversation
This file contains 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
Updated the resource page's next free time button's english text.
Universal field does not follow metafield requirements. Previously my premises page assumed universal field is not required. This change makes universal field always required in my premises page when a resource has universal field defined.
Bumps [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) from 6.0.1 to 6.1.2. - [Release notes](https://github.com/webpack/webpack-dev-middleware/releases) - [Changelog](https://github.com/webpack/webpack-dev-middleware/blob/v6.1.2/CHANGELOG.md) - [Commits](webpack/webpack-dev-middleware@v6.0.1...v6.1.2) --- updated-dependencies: - dependency-name: webpack-dev-middleware dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
…bpack-dev-middleware-6.1.2 Bump webpack-dev-middleware from 6.0.1 to 6.1.2
Bumps [express](https://github.com/expressjs/express) from 4.17.3 to 4.19.2. - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/master/History.md) - [Commits](expressjs/express@4.17.3...4.19.2) --- updated-dependencies: - dependency-name: express dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [tar](https://github.com/isaacs/node-tar) from 6.1.13 to 6.2.1. - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v6.1.13...v6.2.1) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Previously when admin selected to edit a reservation via manage reservations page using reservation page, it was possible to select time slot incorrectly. This happened because reservation page did not get correct slot size info from manage reservations page. This change fixes the issue by making sure slot size is given correctly when using reservation page to edit reservations.
…press-4.19.2 Bump express from 4.17.3 to 4.19.2
…r-6.2.1 Bump tar from 6.1.13 to 6.2.1
Most notable changes: - added a new overnight calendar component - overnight calendar is shown when resource is set to be in overnight mode (resource and reservation pages) - all time fields support times and durations in overnight situations
Overnight reservations don't work in admin resources page. This change labels overnight resources as unusable in admin resource page and disables slot usage and displaying of reservations.
Reservations of type blocked should not have cooldown. This change handles skipping blocked reservations in cooldown checks in both resource/reservation page and in admin resources page.
Changed min period rule to only be skippable by unit admins and superusers. Changed other staff checks to check user to have at least unit manager instead of any unit permission.
Admin users will now have all external links within a dropdown menu 'Links'.
Changed format "dd.mm.yyyy HH:mm - dd.mm.yyyy HH:mm" to include finnish or swedish time prefix klo/kl. e.g. "20.10.2010 klo 10:00 - 20.11.2010 klo 12:00".
When editing some own reservation, cooldown was not shown correctly on own other reservations. This change fixes the issue by showing cooldown on user's other reservations. Only the currently selected reservation to edit does not have cooldown.
New select rules are following: - first selection is start date - if start exists and second selection is before start, start is moved to selected - if start is selected again, its selection is removed - if start is selected and second selection is after start, selection is end - if both start and end are selected, new selection is new start and end is removed Changed validation and calendar 'modifiers' to fit the new ruleset
Normal users can't reserve same day after overnight start time. Admins can bypass this deadline.
…ar (#327) Special style rules for own reservation in history when editing were missing. This change fixes the missing styles issue.
…328) Instead of showing general "something went wrong" error notification, period collision errors will show new more specific error notification.
Previously continous reservation check did not correctly detect reservations that last 24hrs or less. This change fixes the issue.
Previously when overnight start and end time were the same time, continous reservation check would falsely detect next and previous day selections to break continous selection. This change fixes the issue.
Previously when user selected a date after a blocked date as start date and then selected a new start date on a date where start date is not allowed (i.e. next day is blocked) the check would allow this. This change fixes the issue.
ezkat
approved these changes
Jun 4, 2024
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.
Some notable changes: