Open ArakTaiRoth opened 10 months ago
:tada: This issue has been resolved in version 4.16.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 1.16.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 2.6.0-alpha.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 2.6.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
what is the status of this issue? Where does angular type safety fall on the roadmap for this project?
I see @chrisolsen mentioned this in a PR but it was unclear as to the state of things.. I can only assume it still doesn't work based on this being still open.
@cjam Angular wrapping components are currently in progress.
@chrisolsen I'm sure you're already aware of all the work Mitch R did, but in the event that you are not he has wrapped all / most of the components from this library over here:
Perhaps it could just be pulled in and maintained in here by your team instead of externally.
Thanks @cjam, but I don't have an EMU account so I don't have access to that repo. Would it be possible to send me the zip file via Slack?
Info
Currently there is no type safety with Angular. We ask people to implement
CUSTOM_ELEMENTS_SCHEMA
when they import our packages. By doing this, it disables type safety for their application, which is not desirable. This disables things like failing builds if they misspell a property or use a property that doesn't exist. They expect the application to work, and it doesn't, but there was no build error, so they're left to figure it out on their own what the issue is.We have seen teams build their own Angular wrappers around our components to combat this issue. But that's a lot of work to hoist onto every other Angular team.
Options
We have come up with a few things that could be options:
We aren't exclusive to the options listed above, if there is another option that we haven't presented that could be better, please investigate it.
Acceptance Criteria:
We have a list of options that could work (what was listed above, we don't know it will actually work). With an idea for each one on effort to implement, how much it will effect our users (effort for them), and how effective it will be at solving the issue.