Document and validate ArgumentTypes#resource limitations
Open
Nobody has claimed this yet.
priority: low
status: accepted
type: bug
version: 1.21
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
Usage of the argument type with registries not synced with the client errors during registration and is documented as such in the javadocs.
Observed/Actual behavior
Usage of the argument type with registries not synced with the client blows up during connection.
Steps/models to reproduce
N/A
Plugin and Datapack List
N/A
Paper version
N/A
Other
N/A
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 API definition and javadocs for ArgumentTypes#resource. Compare how registries that are not synced with the client behave during registration and connection, then document and validate the limitation so the behavior matches the stated expectation. No specific file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100