-
Notifications
You must be signed in to change notification settings - Fork 360
Fixed Issue #193 #195
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
Fixed Issue #193 #195
Conversation
…actored codegens accordingly
Fixed global namespace imports for shelljs having potential for conflict with local functions in future and refactored all codegens respectively. Also fixed it for boilerplate in order to avoid this while bootstrapping for new language/framework. @umeshp7 Approval required. |
@shreys7 Review required |
@nikhilmuz I have reviewed the code. Can you just check once if the following commands work perfectly after the changes? in the root repo:
cd inside any codegen
|
I have done lint test inside every codegen. It passes. I will do remaining
tests and will update you.
…On Wed, 18 Mar, 2020, 12:39 pm Shrey Shah, ***@***.***> wrote:
@nikhilmuz <https://github.com/nikhilmuz> I have reviewed the code. Can
you just check once if the following commands work perfectly after the
changes?
in the root repo:
- npm run test
- npm run test <codegen-name>
cd inside any codegen
- npm run test
- npm run test-unit
- npm run test-lint
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#195 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEZUYF5NTOEGZE7NMLKWH2DRIBXSXANCNFSM4LAYN7PA>
.
|
@shreys7 I have done lint test on all the codegens locally |
Merging this, thanks for the contribution 😄 |
Refactored global namespase import for shelljs in boilerplate and refactored codegens accordingly as per issue #193