feat: add close button to app resources - #8137
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAppResources/Editor.tsx now integrates React Router's ChangesClose Button Navigation
🚥 Pre-merge checks | ✅ 5 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Actionable comments posted: 0 |
g1rly-c0d3r
left a comment
There was a problem hiding this comment.
- Open every type of app resource and form definition
- Verify that 'Close' closes the resource view
- Open every type of app resource and form definition and make a change
- Verify that you see the "Are you sure you want to leave this page?" warning
Looks good! The close button does take you back to *.specifysystems.org/specify/resources.
I did notice that in the form editor, if there is an XML parsing error, the "Are you sure you want to leave this page?" warning does not appear. This seemed to only happen if that was the first edit that I made, though.
emenslin
left a comment
There was a problem hiding this comment.
- Open every type of app resource and form definition
- Verify that 'Close' closes the resource view
- Open every type of app resource and form definition and make a change
- Verify that you see the "Are you sure you want to leave this page?" warning
Looks good, I checked every type of resource and all work as expected.

Fixes #8136
This PR adds a "Close" button to all app resources. This routes the user back to the main app resource page, as if they had not selected anything. If there are unsaved changes, the user will be warned before proceeding.
Checklist
self-explanatory (or properly documented)
Testing instructions
Summary by CodeRabbit