-
Notifications
You must be signed in to change notification settings - Fork 660
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
Discuss: Deprecate/Remove state command #904
Comments
tlancina
changed the title
Deprecate/Remove state command
Discuss: Deprecate/Remove state command
Apr 19, 2016
This was referenced May 2, 2016
There's even a SO question about the topic so yes, indeed there's many people confused what to choose (and probably doubly confused when different team members are mixing cordova and ionic commands) |
Yesterday, i've installed new ionic CLI beta version and facing the same issue when trying to compile an ionic 1 code version... |
Closing in favor of #1324. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The state command was created to manage Cordova plugins before it was supported in Cordova. Cordova now manages plugins and platforms in config.xml: https://cordova.apache.org/docs/en/latest/platform_plugin_versioning_ref/index.html so there is a decent amount of confusion between the Ionic and Cordova behavior. As Cordova platforms and plugins are not an Ionic concern, let's deprecate the state command and document the existing Cordova command workflow, ie
plugin add --save
.The text was updated successfully, but these errors were encountered: