As an industrial reporter, I want to enter general stationary combustion (GSC) emissions in my report, so that I can fulfill my reporting obligations

[pbastia]

Description:

blocked by #256

Wireframe:

This is the first form we implement fully following the minispike It is meant to also test how to handle the uiSchema and field ordering

This is about generating the form from what the API returns

Brief description of the work involved, including any user research context or key decisions.

Saving the data entered in this form is not a requirement for this ticket as we don't have the data structures defined yet for how we're going to store our reporting data in the database.

Acceptance Criteria:

Given I am on the general stationary combustion activity form page When I first land on the page Then the base schema (non-conditional) parts of the form are displayed

Given the base schema has rendered correctly When I enter a gas type Then the fields that are conditional on gas type are dynamically added to the form

Given the gas type data has been entered When I enter a methodology Then the fields that are conditional on methodoology are dynamically added to the form

Development Checklist:

• [ ] GSC page fetches the base schema from the API service on initial load
• [ ] Conditional gas type fields render dynamically
• [ ] Conditional methodology fields render dynamically
• [ ] Options for how to apply the UI Schema & where to store it have been explored & documented
• [ ] Matches the wireframe
• [ ] Tested with Vitest
• [ ] Documentation on how to generate a form from a configuration

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if required)
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

• [ ] Acceptance criteria are tested by the CI pipeline
• [ ] UI meets accessibility requirements
• [ ] Configuration changes are documented, documentation and designs are updated
• [ ] Passes code peer-review
• [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
• [ ] Ticket is ready to be merged to main branch
• [ ] Can be demoed in Sprint Review
• [ ] Bugs or future work cards are identified and created
• [ ] Reviewed and approved by Product Owner

Blocking

271

272

Notes:

-

[pbastia]

@patriciarussellCAS 👀

[patriciarussellCAS]

Flagging that we are not including the "allocation of emissions" section - this is still being confirmed by BA.