You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Internally, we've migrated to the planned 1.0 config format - we parse the original format, then do a conversion to the new structure. The new structure is set up with serialization and deserialization routes that makes it theoretically possible to read the new files - but nothing is set up to actually do so. Our final steps to complete this migration will be:
Introduce parallel deserialization of both config formats. We need to keep being able to read the old format to report to users that they need to upgrade, and so that we can:
Use dist init to read the old config format and migrate to the new one, and then use that new format as the basis for edits we make to the user's config files on their behalf. This should allow us to painlessly migrate everyone to the new format.
My plan is that when we introduce this, any commands except init will refuse to run if they're loaded from the old config files, but can use that as information to notify users that they need to upgrade via dist init.
The text was updated successfully, but these errors were encountered:
I did a quick look at the TomlLayer to confirm, and we are definitely set for serializing and deserializing it from TOML files. Here's a sample of taking dist's own existing v0 config, passing it through the TomlLayer upconversion carousel, and then serializing it to disk.
Internally, we've migrated to the planned 1.0 config format - we parse the original format, then do a conversion to the new structure. The new structure is set up with serialization and deserialization routes that makes it theoretically possible to read the new files - but nothing is set up to actually do so. Our final steps to complete this migration will be:
dist init
to read the old config format and migrate to the new one, and then use that new format as the basis for edits we make to the user's config files on their behalf. This should allow us to painlessly migrate everyone to the new format.My plan is that when we introduce this, any commands except
init
will refuse to run if they're loaded from the old config files, but can use that as information to notify users that they need to upgrade viadist init
.The text was updated successfully, but these errors were encountered: