-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix Typescript Arrow Consts needing using the filename #209
Conversation
Thanks @jrwpatterson ! We'll review and update. |
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.
Thanks for submitting this PR! A few comments but nothing major.
...li/src/steps/serialization/component/implementation/typescript/component/getComponentName.ts
Outdated
Show resolved
Hide resolved
...li/src/steps/serialization/component/implementation/typescript/component/getComponentName.ts
Outdated
Show resolved
Hide resolved
...li/src/steps/serialization/component/implementation/typescript/component/getComponentName.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Victor Adossi <61000371+vados-xenon@users.noreply.github.com>
@vados-xenon I have accepted your comments thank you |
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.
Thank you very much for your PR @jrwpatterson
Looks good to me 👍
This PR should fix the fact that the latest release of Arrow names needs the filenames to be in ProperCase because the arrow-function implementation is a child of the actual component. This means that in getComponentName it was falling back to the filename and dumping components such as
import simple-select from '../src/components/simple-select.tsx
in the components.js file in the .uxpin-mergeI don't think it will affect any other way of importing when using typescript.