Skip to content

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

Merged
merged 12 commits into from
May 13, 2019

Conversation

VladimirAmiorkov
Copy link

@VladimirAmiorkov VladimirAmiorkov commented May 7, 2019

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 the tns 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

@ghost ghost assigned VladimirAmiorkov May 7, 2019
@ghost ghost added the new PR label May 7, 2019
@cla-bot cla-bot bot added the cla: yes label May 7, 2019
@VladimirAmiorkov VladimirAmiorkov changed the title feat: use online templates to create demo applications 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 May 7, 2019
@VladimirAmiorkov VladimirAmiorkov requested a review from a team May 7, 2019 15:33
@VladimirAmiorkov VladimirAmiorkov changed the title 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 [DO NOT MERGE] 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 May 8, 2019
feat: make it possible for the user to choose what kind of demos (by framework) to be included #128
@VladimirAmiorkov VladimirAmiorkov force-pushed the amiorkov/scripts-imrpvements branch from 3ce2e49 to 3e824c3 Compare May 9, 2019 12:44
@VladimirAmiorkov VladimirAmiorkov changed the title [DO NOT MERGE] 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 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 May 12, 2019
.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
Copy link

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

Copy link
Author

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

@VladimirAmiorkov VladimirAmiorkov merged commit 860d8ac into master May 13, 2019
@ghost ghost removed the new PR label May 13, 2019
@VladimirAmiorkov VladimirAmiorkov deleted the amiorkov/scripts-imrpvements branch May 13, 2019 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants