Split SessionsPage into subpages
#776
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a very large PR which splits the massive
SessionsPageinto the subpages:SessionsChildrenPageSessionsConsentPageSessionsEditPageSessionsOverviewPageSessionsPatientPageSessionsPatientSessionActivityPageSessionsPsdPageSessionsRecordVaccinationsPageSessionsRegisterPageSessionsSearchPageSessionsTriagePageSessionsVaccinationWizardPageThis makes the file
sessions.pyeasier to read, understand and work on. It also makes our code adhere more strictly to the Playwright POM. Some other things happened unintentionally during this refactor which would be pretty annoying to split into other commits / PRs:There are some less positive effects that this PR has:
sessions.pyis still very largeThese will be addressed in future PRs.
Due to AI usage etc, the split was done all at once which makes it very hard to review. At the very least, it would be worth checking that the new page objects have appropriate names.