ansys / ansys/scade-design-rules
TODO tracking list
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue is for keeping track of existing to-dos (line nos might not be exact):
- tools/check_doc/update_cod.py line 126
- src/ansys/scade/design_rules/annotations/ann_notes_for_basic_interface_types.py line 149
- src/ansys/scade/design_rules/naming/camel_case_naming.py line 91
- src/ansys/scade/design_rules/naming/name_structure_diagram line 79
- src/ansys/scade/design_rules/naming/name_structure_diagram line 83
- src/ansys/scade/design_rules/project_structure/no_scade_library.py line 103
- src/ansys/scade/design_rules/traceability/has_link_or_part_of_equationset.py line 141
- tests/annotations/test_ann_notes_for_basic_interface_types.py line 82
- tests/annotations/test_ann_notes_for_basic_interface_types.py line 102
- tests/annotations/test_ann_notes_for_basic_interface_types.py line 106
Contributor guide
Research direction
Review the TODO locations listed in tools/check_doc/update_cod.py, the design-rule files under src/ansys/scade/design_rules/, and the two test files under tests/annotations/. Start by reading each TODO in context and the related tests. Done means the listed TODOs have been resolved and the affected tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100