playframework / playframework/playframework
Java packages for ApplicationProvider must be consistent Scala version
Open
Nobody has claimed this yet.
type:improvement
- Dominant language
- Scala
- Stars
- 12.6k
- Forks
- 4k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 29
Description
We usually have play.api.something for Scala and play.something for Java. This is not consistent for ApplicationProvider:
- Java version is
play.server.ApplicationProvider - Scala version is
play.core.ApplicationProvider
See https://github.com/playframework/playframework/pull/7300#pullrequestreview-36584049.
Contributor guide
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 by locating the Java and Scala ApplicationProvider definitions referenced in the issue, then review pull request #7300 and its review discussion. Done means the two packages follow the project's Java/Scala naming convention consistently and affected references still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100