SAP / SAP/ui5-language-assistant
Investigate edge cases of Aggregations used as an attribute
Open
Nobody has claimed this yet.
Tech Debt
- Dominant language
- TypeScript
- Stars
- 59
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Should an aggregation without AltTypes:
- Raise an issue when used as an attribute? should it be unknown attribute error?
- if deprecated raise a deprecated warning when using as an attribute?
- Can there be namespace conflicts between aggregations/props/events/assosiations?
- Is this possible namespace conflict depend on the altTypes prop?
- TODO: examine api.json are all members in a single dictionary thus prevent the conflict?
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
Start by examining api.json to determine whether aggregations, props, events, and associations share one namespace and how AltTypes are represented. Investigate the expected behavior for aggregations without AltTypes, including unknown-attribute and deprecation handling, then record the decisions and any required tests or implementation changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100