Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate edge cases of Aggregations used as an attribute #263

Open
bd82 opened this issue Jul 28, 2020 · 0 comments
Open

Investigate edge cases of Aggregations used as an attribute #263

bd82 opened this issue Jul 28, 2020 · 0 comments

Comments

@bd82
Copy link
Member

bd82 commented Jul 28, 2020

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?
@bd82 bd82 added the Tech Debt label Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant