LaunchCodeEducation / LaunchCodeEducation/java-web-development
[Clarification] Java authentication annotation inconsistency.
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 13
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Permalink:
https://education.launchcode.org/java-web-development/chapters/auth/studio.html
Issue:
From the instructor:
"In the studio of the authentication chapter, the user repository doesn’t include the @repository annotation. This is different than every other repository implementation we’ve done in the past and there’s no context as to why that annotation isn’t required."
From a student:
"In coding events auth and in the auth studio, we do not use the @repository annotation on the user repository, I was wondering why we wouldn't use this annotation when up to this point we have used it? There is a gap in understanding when and when not to use the annotation from the readings and studios."
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the authentication studio at the linked studio.html page and compare its user repository with the repository examples referenced in the chapter. Clarify when @Repository is required and update the studio or nearby explanation so the distinction is explicit; done means students can understand why the authentication example differs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100