TryGhost/Ghost
1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2024-12-16 20:43:01 +03:00
Code Issues Projects Releases Wiki Activity
de1a9abe76
Ghost/ghost/admin/app/components/modals/confirm-unsaved-changes.hbs

19 lines
814 B
Handlebars
Raw Normal View History

Fixed customize design route-based modal handling + added unsaved change confirmation refs https://github.com/TryGhost/Team/issues/559 refs https://github.com/TryGhost/Team/issues/1045 - removed need for `{{will-destroy}}` in the modal template by using `willTransition()` in the route that opened the modal instead - used the property of new modals acting as promises to implement an unsaved changes confirmation modal - added `confirmUnsavedChanges()` method that opens a "are you sure you want to leave?" modal that is treated as a promise. If the modal is closed by the "Leave" button the promise returns true in which case we rollback the unsaved changes. The modal is returned so that other behaviour can use this method and wait for the confirmation result - added `willTransition()` route hook that calls `confirmUnsavedChanges()` when there are unsaved changes and will only continue to transition if the "Leave" button is pressed - added `beforeClose()` hook to the customize modal when opening so that we can prevent the customize modal from closing when "Stay" is clicked in the confirmation modal - updated `activate()` hook to store the modal instance so it can be closed later - updated `deactivate()` hook to call `.close()` on the modal instance rather than using private data/methods on the modals service
2021-09-16 22:26:49 +03:00
<div class="modal-content">
<header class="modal-header" data-test-modal="unsaved-settings">
<h1>Are you sure you want to leave this page?</h1>
</header>
Fixed close button in confirm modal causing navigation no issue - using an `<a>` instead of a `<button>` meant that the anchor link's default behaviour was being triggered when clicked leading to the browser navigating back to the dashboard
2021-09-30 18:26:20 +03:00
<button type="button" class="close" role="button" title="Close" {{on "click" @close}}>{{svg-jar "close"}}<span class="hidden">Close</span></button>
Fixed customize design route-based modal handling + added unsaved change confirmation refs https://github.com/TryGhost/Team/issues/559 refs https://github.com/TryGhost/Team/issues/1045 - removed need for `{{will-destroy}}` in the modal template by using `willTransition()` in the route that opened the modal instead - used the property of new modals acting as promises to implement an unsaved changes confirmation modal - added `confirmUnsavedChanges()` method that opens a "are you sure you want to leave?" modal that is treated as a promise. If the modal is closed by the "Leave" button the promise returns true in which case we rollback the unsaved changes. The modal is returned so that other behaviour can use this method and wait for the confirmation result - added `willTransition()` route hook that calls `confirmUnsavedChanges()` when there are unsaved changes and will only continue to transition if the "Leave" button is pressed - added `beforeClose()` hook to the customize modal when opening so that we can prevent the customize modal from closing when "Stay" is clicked in the confirmation modal - updated `activate()` hook to store the modal instance so it can be closed later - updated `deactivate()` hook to call `.close()` on the modal instance rather than using private data/methods on the modals service
2021-09-16 22:26:49 +03:00
<div class="modal-body">
<p>
Hey there! It looks like you didn't save the changes you made.
</p>
<p>Save before you go!</p>
</div>
<div class="modal-footer">
[chore] adds ember-template-lint and fixes all fixable issues (#2238) no issue - This will help with the octane migration and you can still run the lint rules even when they are todos. (Checkout the docs at https://github.com/ember-template-lint/ember-template-lint/blob/158b1196676489b4bfc01f851b46d3aecd2b314e/docs/todos.md) The good news is any new code will be checked against the recommended config. - I fixed all the auto fixable things we could get in this PR as well
2022-02-02 19:09:43 +03:00
<button class="gh-btn" data-test-stay-button type="button" {{on "click" (fn @close false)}}><span>Stay</span></button>
<button class="gh-btn gh-btn-red" data-test-leave-button type="button" {{on "click" (fn @close true)}}><span>Leave</span></button>
Fixed customize design route-based modal handling + added unsaved change confirmation refs https://github.com/TryGhost/Team/issues/559 refs https://github.com/TryGhost/Team/issues/1045 - removed need for `{{will-destroy}}` in the modal template by using `willTransition()` in the route that opened the modal instead - used the property of new modals acting as promises to implement an unsaved changes confirmation modal - added `confirmUnsavedChanges()` method that opens a "are you sure you want to leave?" modal that is treated as a promise. If the modal is closed by the "Leave" button the promise returns true in which case we rollback the unsaved changes. The modal is returned so that other behaviour can use this method and wait for the confirmation result - added `willTransition()` route hook that calls `confirmUnsavedChanges()` when there are unsaved changes and will only continue to transition if the "Leave" button is pressed - added `beforeClose()` hook to the customize modal when opening so that we can prevent the customize modal from closing when "Stay" is clicked in the confirmation modal - updated `activate()` hook to store the modal instance so it can be closed later - updated `deactivate()` hook to call `.close()` on the modal instance rather than using private data/methods on the modals service
2021-09-16 22:26:49 +03:00
</div>
</div>
Reference in New Issue Copy Permalink