Skip to content
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

feat (schematics): allow comments in angular.json file (Issue #480) #550

Merged
merged 8 commits into from
Jun 5, 2020

Conversation

atao60
Copy link
Contributor

@atao60 atao60 commented May 14, 2020

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • [ x] Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Other... Please describe:

What is the current behavior?

Issue Number: #480

What is the new behavior?

Allow comments in angular.json file with Scully schematics
In fact allow json5 syntax as Angular itself.
Note. ATM json5 is allowed only with angular.json files. But it'd be very easy to extend it to any json file of your choice.

Does this PR introduce a breaking change?

  • Yes
  • [x ] No

Other information

This is a sequel of pr #531, as in the meantime the folder schematics/scully has been moved to libs/scully-schematics.

@atao60 atao60 changed the title Issue480 Issue480: allow comments in angular.json file May 14, 2020
@atao60 atao60 closed this May 14, 2020
@atao60 atao60 reopened this May 14, 2020
@atao60 atao60 closed this May 14, 2020
@atao60 atao60 reopened this May 14, 2020
@atao60 atao60 changed the title Issue480: allow comments in angular.json file Issue #480: allow comments in angular.json file May 14, 2020
@atao60 atao60 changed the title Issue #480: allow comments in angular.json file feat (schematics): allow comments in angular.json file (Issue #480) May 17, 2020
@atao60
Copy link
Contributor Author

atao60 commented May 22, 2020

It seems this pr is stuck. May be because replacing pr #531 just after @SanderElias assigned the review of this last one to @jorgeucano.
@SanderElias, may I ask the review of the present one to be reassigned to @jorgeucano?

@@ -15,7 +15,9 @@
"test": "tsc -p tsconfig.spec.json && jasmine src/**/*_spec.js",
"publish:patch": "tsc -p ./tsconfig.json && npm version patch && npm publish --access public",
"publish:minor": "tsc -p ./tsconfig.json && npm version minor && npm publish --access public",
"publish:major": "tsc -p ./tsconfig.json && npm version major && npm publish --access public"
"publish:major": "tsc -p ./tsconfig.json && npm version major && npm publish --access public",
"clean": "rimraf spec/**/*.js spec/**/*.d.ts spec/**/*.js.map src/**/*.js src/**/*.d.ts src/**/*.js.map",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why you add this?

Copy link
Contributor Author

@atao60 atao60 May 25, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's just a dev convenience to get a clean state before each build on workstation. Not needed during CI Build.
Can be removed if you wish.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove this and I will approve! thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jorgeucano jorgeucano merged commit 9746ed2 into scullyio:master Jun 5, 2020
@atao60 atao60 deleted the issue480 branch June 5, 2020 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants