Create XML upgrader so we can fix naming without issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
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.
Description
This issue has no description.
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10d 13h
- Merged PRs (30d)
- 1
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.
More from ldtteam/BlockUI
-
Bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Bug
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
Enhancement / Change Request
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Enhancement / Change Request
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100