Skip to content

Conversation

SBurns002
Copy link
Contributor

@SBurns002 SBurns002 commented Sep 19, 2025

Pull Request Review Checklist

Code Quality

  • Code follows project style guidelines (Google Java Style for backend, ESLint/Prettier for frontend)
  • Code is readable, maintainable, and uses clear naming
  • No unnecessary or commented-out code

Functionality

  • Code runs as intended and solves the issue/feature described
  • No breaking changes introduced without justification
  • Input validation and error handling are in place

Testing

  • Unit tests or integration tests cover new/changed logic
  • All existing tests pass
  • Manual testing steps (if any) are described in the PR

Security & Stability

  • No secrets, credentials, or sensitive data committed
  • SQL queries, API calls, or file operations are safe from injection or misuse
  • Dependencies added are necessary and from trusted sources

Project Process

  • Branch name and commit messages follow team conventions
  • PR is scoped to a single feature or fix (not overloaded)
  • Documentation, comments, or README updates provided if needed

sdavies39219 added 3 commits September 17, 2025 22:59
…d, added application-test.properties with dummy data, added authenticationEntryPoint so we get 401s instead of 403s, kept the key generator just in case, added checks to see what env we are in and autogenerate token if needed and persist locally.
sdavies39219 added 2 commits September 22, 2025 10:08
@SBurns002 SBurns002 merged commit 8c3bbee into dev Sep 22, 2025
4 checks passed
@prlara23Pro prlara23Pro deleted the stacey_dev_2.0 branch September 27, 2025 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants