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
Replace hardcoded config fallback version with dynamic constant (#381)
* Replace hardcoded config fallback version with dynamic constant
Previously, when loading the config file, the fallback version `”0.3.0"` was hardcoded
to handle unversioned configs from earlier releases.
This commit replaces the hardcoded value with the centralized `version` constant,
ensuring consistency across the codebase and reducing the risk of version mismatches
in the future.
* Make `version` field in config mandatory and remove fallback logic
This commit aligns with the decision to drop support for configurations without a version field (pre-0.3.0). The `version` property in `Config` is now non-optional and must be explicitly set at creation.
- Removed the fallback assignment to "0.3.0"
- Updated all code to require and use non-optional `version`
- Adjusted the config initializer to take `version` as a parameter
- Simplified conditional checks and eliminated `.version?`
This ensures that swiftly no longer silently accepts or upgrades legacy configurations without an explicit version.
* Fix test build by adding required `version` to Config initializers
* Apply Swift formatting using `swiftformat` on Sources and Tests
0 commit comments