Handle reserved function names in binding and implementation languages
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating the code that processes component binding and implementation sections and generates language-specific names. Review how C# methods such as GetType are currently emitted, then determine how the proposed reserved-name replacement would be represented and applied. Done means a binding can declare a replacement and generated C# occurrences use the replacement without altering other languages.
Written by the indexing model from the issue text.
Description
Different languages define specific methods on classes per default, e.g. C# defines ToString, GetType and GetHashCode.
When components define methods with these names in one of their classes, this can lead to problems.
Solution:
in the binding (or implementation section) of the component, define overrides for these resreved names or keywords
e.g.
<binding language="CSharp" indentation="tabs">
<rerserved name="GetType" replacement="GetObjectType"/>
</binding>
This would basically replace each occurrence of "GetType" in the C#-binding by "GetObjectType".
- 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 3/5 1-2 days Newbie friendliness 35/100
Autodesk/AutomaticComponentToolkit#188 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Autodesk/AutomaticComponentToolkit#183 · 1 comment ·
-
Autodesk/AutomaticComponentToolkit#162 · 1 reaction · 2 assignees ·
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