XML namespaces are not observed
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the issue with the ACT XML example containing a non-default namespace and a same-named attribute, then trace the compiler's XML parsing and attribute lookup. Confirm the fix by checking that the generated enum uses the intended attribute value rather than the namespaced value.
Written by the indexing model from the issue text.
Description
If the ACT xml file contains a namespace other than the default and an attribute has the same name the compiler generates using the last value. For example,
<enum name="Foo">
<option name="Bar" ns:name="Bob"
...generates...
enum Foo {
Bob =
}
- Dominant language
- Go
- Stars
- 54
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
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 Autodesk/AutomaticComponentToolkit
-
Autodesk/AutomaticComponentToolkit#226 · 5 comments · 3 reactions · 3 assignees ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Autodesk/AutomaticComponentToolkit#213 · 1 comment · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Autodesk/AutomaticComponentToolkit#183 · 1 comment ·
-
Autodesk/AutomaticComponentToolkit#162 · 1 reaction · 2 assignees ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Autodesk/AutomaticComponentToolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug group: validation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
codecheckers/chekhov#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100