fix object syntax css prop, support more types of components & custom elements #229
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
quantizor
force-pushed
the
changes-revised
branch
from
be0934c
to
bec8201
Compare
|
Going to take a second pass at #228 tonight and see if I can get it working consistently before I cut another patch release. If I can't get it where it needs to be will do a patch with these changes tomorrow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reduced version of #228 since the injection location code isn't totally ready yet
fix transpilation of objects being passed into the css prop
modifications from @bpierre to support custom elements, lowercase component variable names with dots, nested component names with dots