Implemented Route Testing for Issue 1489 #1568
Open
+871
−472
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
squid game
…tizer imports and tests"
…ss/failure responses
…fy sanitizer and patch XSS in success/failure responses"
up to date. package-lock.json and package.json should match now.
Cross Site Scripting fix.
Normalize all line endings to LF
Changed the installOED.sh file to generate randomized values for OED_TOKEN_SECRET and POSTGRES_PASSWORD, which are then stored in .env file. Changed docker.compose.yml to draw from the .env file if variables exist there. When in dev mode with the default values the user will be warned in the console when OED is started. Also implemented a warning for the mailing variables, if the method is set and a default remains in the rest the user will be warned in production.
Remove line endings fix, will be implemented separately.
Restoring default value of OED_PRODUCTION
Added meeting notes for the client meeting held on November 5, 2025, including agenda items and group progress updates.
Updated meeting notes with group progress and mentor suggestions.
Added meeting notes for the client meeting on November 12th, 2025.
Added meeting notes for client meeting on November 12th, 2025, detailing issues discussed and progress made.
Added each issue as a risk, with probability, impact, and solution.
Add a single instance before the tests
Member
|
Thank you to @Andrew-Bonner for this PR. Two items:
I'm not going to review this PR until these two items are resolved. Please let me know if anything is not clear or you need something. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
Description
(Please include a summary of the change and which issue is touched on. Please also include relevant motivation and context.)
Fixes #[issue]
(In general, OED likes to have at least one issue associated with each pull request. Replace [issue] with the OED GitHub issue number. In the preview you will see an issue description if you hover over that number. You can create one yourself before doing this pull request. This is where details are normally given on what is being addressed. Note you should not use the word "Fixes" if it does not completely address the issue since the issue would automatically be closed on merging the pull request. In that case use "Partly Addresses #[issue].)
Type of change
(Check the ones that apply by placing an "x" instead of the space in the [ ] so it becomes [x])
Checklist
(Note what you have done by placing an "x" instead of the space in the [ ] so it becomes [x]. It is hoped you do all of them.)
Limitations
(Describe any issues that remain or work that should still be done.)