Closed justinlittman closed 2 years ago
@lwrubel Assigning to you for consideration of the proposed change.
Spelling this out since the PR title didn't fully explain what the changes are:
These both make sense to me.
The anti-pattern that @jcoyne is pointing out seems to already be there, if I am understanding correctly. @justinlittman if I am misunderstanding the change on edit, let me know. Depending on this, I will set up a new issue to discuss how to improve the edit/update UI.
The anti pattern doesn't exist at present, because you don't get redirected to the edit page on update presently.
OK, now I understand where I misunderstood the current behavior (had not been looking at a deploy of main to compare with current behavior). Thanks, @jcoyne and @justinlittman.
It seems like as we are adding more features to the app it would be useful to have a show (detail) page with an Edit button. And then we could follow a normal pattern for redirect on update.
Why was this change made? 🤔
Current behavior drives me crazy.
How was this change tested? 🤨
âš¡ âš If this change involves consuming from other services or writing to shared file systems, test that web archive seed and crawl accessioning (and maybe even SWAP system?) works properly in [stage|qa] environment, in addition to specs. âš¡ QA