Allow wrapping any React component with an Angular one on-the-fly #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #103.
I've open for suggestions on the API etc. to see if there are things that can be improved. The main idea is the keep the Angular-React philosophy as much as possible, while simplifying the wrapping of React components.
Notes
Using this is completely optional (no breaking API changes), at the cost of:
NO_ERRORS_SCHEMAin theNgModulethat plans to consume these components. Since these are created at runtime, the Angular compiler can't validate them.Inputs andOutputs, I haven't tested render props, and I expect them to not work at this time. A future PR could improve upon this.Usage
call
wrapComponenton any React component:schemas: [NO_ERRORS_SCHEMA](see notes above for the why).