cDM's history.block(...) code generates a console warning
Description
CSP Request Details
None
CSP Rejection Details
None
Potential Workaround
None
Checklist
hideTestRail: Results
Activity
Show:
John Coburn November 22, 2024 at 3:04 PM
Reeks slightly of ‘StrictMode’ where mounting lightning strikes twice.
Zak Burke November 12, 2024 at 1:32 PM
I think we should close this as “Won’t Do”. final-form has been abandoned, and this is just a warning with no user impact.
Zak Burke May 29, 2021 at 11:00 AM
Looks like the problem is that two separate forms are loaded and displayed simultaneously. Maybe a solution is to pull the form up a level into CheckOut itself instead of wrapping both ItemForm and PatronForm.
Won't Do
Details
Details
Assignee
Unassigned
UnassignedReporter
Zak BurkePriority
P3Development Team
Stripes Force
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 15, 2020 at 7:50 PM
Updated December 23, 2024 at 5:55 PM
Resolved December 23, 2024 at 5:55 PM
TestRail: Cases
TestRail: Runs
The line
this.unblock = history.block(...)incomponentDidMountgenerates a console warning:This is perplexing given that a similar issue at react-router suggests resolving the problem by handling
historyoperations in cDM instead of cWM, but cDM appears to be the problem here :/There is an argument to be made for abandoning stripes-final-form altogether and just using react-router's native
<Prompt>to handle prompt-on-dirty, but that may be a bigger refactor, if also a better end result.