Closed elliottSlee closed 1 year ago
@marcellmueller if we refactored this review page, as was suggested the other day, would some of these errors be fixed? If so, which ones? I'd like to clarify this card before sprint planning.
Maybe ask @matthieu-foucault. I don’t see the value in rebuilding the entire review page instead of some minor bug fixes given the time constraints.
The value is in ensuring code quality, removing code duplication and avoiding future bugs. If we're looking at short term value, then those bugs can definitely be fixed without refactoring, but similar bugs will come up whenever changes are made to the form schema.
Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @matthieu-foucault @wenzowski
Looking good, but just noticing that
in addition to above, I believe this should be a mandatory quesiton:
in addition to above, I believe this should be a mandatory quesiton:
I created #704 and #705 for those two new issues, as they are different bugs than what is listed in this issue's description.
I am a little concerned about this. We made the decision to take the extra time to do the rjsf refactor because it would fix all the bugs on the review page and would remove the need create new bug tickets for the review page and fix them individually thereby saving us effort in the future. After all the effort in the rjsf refactor I am concerned that there are still bugs on the review page, and I wonder if we were better off fixing the bugs piecemeal.
These bugs are not on the review page, but either the JSON Schema itself, or with the way calculated components work. You don't see them until the review page because it's the only place we're doing validation. The fixes will not involve updating the review page, which appears to be doing its job of displaying the form data and JSON schema as specified.
#
#
This doesn't occur if all fields are filled:
#
#
#
#