Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create UI: implement Amalgamation Statement component (aka Court Approval) #18749

Closed
6 tasks done
severinbeauvais opened this issue Nov 24, 2023 · 4 comments
Closed
6 tasks done
Assignees
Labels
ENTITY Business Team good first issue Good for newcomers UX Assurance

Comments

@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Nov 24, 2023

Private Zenhub Image

@severinbeauvais
Copy link
Collaborator Author

@chenhongjing Please see above for new schema property. (Also, we WILL have a courtOrder object in the schema.)

@severinbeauvais severinbeauvais added the good first issue Good for newcomers label Dec 1, 2023
@severinbeauvais severinbeauvais changed the title Create UI: implement Amalgamation Statement component Create UI: implement Amalgamation Statement component (aka Court Approval) Dec 7, 2023
@tshyun24 tshyun24 self-assigned this Dec 20, 2023
@jdyck-fw jdyck-fw removed the monitor label Dec 21, 2023
@yuisotozaki
Copy link

Observation:

  • Select a value and press "Save and Resume Later". Reopen the draft and try to File and Pay. The component is highlighted as "invalid" erroneously even though a value is selected. This behaviour is observed only when the draft is reopened. The component's highlight goes away when the other radio button is selected. However, if "Save and Resume Later" is pressed, the draft reopened, then File and Pay is pressed, the erroneous highlight comes back again.

image.png

@tshyun24
Copy link

tshyun24 commented Jan 8, 2024

Observation:

  • Select a value and press "Save and Resume Later". Reopen the draft and try to File and Pay. The component is highlighted as "invalid" erroneously even though a value is selected. This behaviour is observed only when the draft is reopened. The component's highlight goes away when the other radio button is selected. However, if "Save and Resume Later" is pressed, the draft reopened, then File and Pay is pressed, the erroneous highlight comes back again.

image.png

Should works now!

@yuisotozaki
Copy link

Looks good! Ready for QA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ENTITY Business Team good first issue Good for newcomers UX Assurance
Projects
None yet
Development

No branches or pull requests

5 participants