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

cmd: config format migration strategy #584

Open
bobheadxi opened this issue Feb 24, 2019 · 0 comments
Open

cmd: config format migration strategy #584

bobheadxi opened this issue Feb 24, 2019 · 0 comments
Labels
:cmd command line and clientside functionality type: ux 🎨 the user experience
Milestone

Comments

@bobheadxi
Copy link
Member

Right now if config is mismatched, Inertia just sort of quietly overwrites and throws away anything from a pervious format. We need to work out:

  1. a strategy for executing format migrations
  2. a command to do so

The new command chain from #577 makes things a little awkward for where to put a potential migrate command - I'd like to avoid introducing a inertia config, but inertia migrate seems too trivial for a top-level command, and inertia project migrate + inertia remote migrate seems awks (especially the latter)

Maybe migrations can be done silently by inertia as well

@bobheadxi bobheadxi added :cmd command line and clientside functionality type: ux 🎨 the user experience labels Feb 24, 2019
@bobheadxi bobheadxi added this to the future milestone Feb 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:cmd command line and clientside functionality type: ux 🎨 the user experience
Projects
None yet
Development

No branches or pull requests

1 participant