jarkonik / jarkonik/bevy_scriptum
Make API accept `Into<String>` instead of `String` where possible
Open
enhancement
good first issue
- Dominant language
- Rust
- Stars
- 171
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
Research direction
Start by locating the public API signatures that currently require String and identify which parameters can accept Into without changing behavior. Done means the applicable API parameters use the broader input type and the existing project checks still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, game-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100