Skip to content

Project version in .angular-cli.json #4784

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

Closed
dzonatan opened this issue Feb 17, 2017 · 3 comments
Closed

Project version in .angular-cli.json #4784

dzonatan opened this issue Feb 17, 2017 · 3 comments

Comments

@dzonatan
Copy link
Contributor

Is there any need of having project version property in .angular-cli.json?

"project": {
  "version": "1.0.0-beta.32.3", 
  "name": "my-project-name"
}

Sometimes it might be misleading (especially for ones who are not familiar with angular-cli yet) if you're not manually keeping it in sync with real one used in package.json.
After update/init command deprecation it's so easy to miss to update it... 😞

Meligy added a commit to Meligy/angular-cli that referenced this issue Feb 17, 2017
Adds a note about updating the version number in `.angular-cli.json`
Fixes angular#4784
@dzonatan
Copy link
Contributor Author

shit, accidentally clicked close button but as I see @Meligy and @filipesilva noticed it anyway. :D You're fabulous! 🍻

@filipesilva
Copy link
Contributor

#4795 💃

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants