-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add support for export default #55
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll rereview after the unrelated style changes are rebased out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great overall, thanks! I’m a bit hesitant about the camelize/capitalize approach, but i don’t have a better suggestion.
I wonder if it would be better to leave it anonymous in that case, but set the displayName property to directly match the filename?
ff409ef
to
fcda0e3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like only a few more small tweaks.
It’d still be nice to combine the “with defaults” code more into the buildSvg code, since there’s so much repeated.
anything else that needs fixing ? |
should i just close this ? im using it in a project and everything is working, but i can just make a private repo and use that |
@jb-san please don't; sorry for the delays but my time is limited. I'll plan to merge and release this as soon as i can. |
this adds the ability to do
export { default } from ...
andexport { default as Icon } from ...
this is my first time doing anything with babel, so criticism is welcome..