Create XML upgrader so we can fix naming without issues
Open
Nobody has claimed this yet.
Next Major Version
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10d 13h
- Merged PRs (30d)
- 1
Description
This issue has no description.
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
The issue names no files, tests, or entry points, so start by locating the XML loading and naming-related code in the BlockUI repository. Clarify which naming changes the upgrader must support and how upgraded XML will be detected or validated. Done should mean the intended naming migration works without requiring manual issue-by-issue fixes, with tests covering the supported upgrade behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100