-
-
Notifications
You must be signed in to change notification settings - Fork 54
feat: make it possible for the user to choose what kind of demos (by framework) to be included and create them from online templates #128 #129
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
Conversation
feat: make it possible for the user to choose what kind of demos (by framework) to be included #128
3ce2e49
to
3e824c3
Compare
chore: remove some unit tests as they are not needed
.travis.yml
Outdated
@@ -16,7 +16,7 @@ matrix: | |||
jdk: oraclejdk8 | |||
before_install: nvm install 8 | |||
script: | |||
- cd src && npm i && npm run tsc && cd ../demo | |||
- cd src && npm i && npm run tsc && npm run postclone gitHubUsername=TheGitHubUser pluginName=ThePlugin initGit=y includeTypescriptDemo=y includeAngularDemo=n && cd ../demo |
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 still feel, that the npm i
should be included in the scripts build/tsc instead of in the travis configuration
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.
Actually the postclone script has npm i
in it so we do not need anything to have install since the first and only script that is required to be executed first is npm run postclone
. I will remove this from the travis
PR Checklist
What is the current behavior?
When the
postclone
script is executed updated the already present demo application in the seed.What is the new behavior?
When the
postclone
script is executed it will ask the user which framework type application he wants to be created in the repo and those applications will be created directly from thetns create
command which uses the online templates.Fixes/Implements/Closes #[Issue Number].
#128
BREAKING CHANGES:
The demo application in the seed is deleted
The included "empty" unit test in the demo app is no longer present.
Migration:
As the unit tests are something that is changing over time it is best to manually follow the latest version of the https://docs.nativescript.org/tooling/testing/testing article and execute its commands to initialize unit tests structure in the apps.
There are no longer any included unit tests to the apps
Travis now only builds the app and does not run any unit tests