-
Notifications
You must be signed in to change notification settings - Fork 2
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
Even more backwards compatible (well sort of) #616
Even more backwards compatible (well sort of) #616
Conversation
return invalid([ | ||
`plugin ${s.plugin(id)} has a v${s.code((plugin.rcFile.version ?? 1).toString())} ${s.code( | ||
'.toolkitrc.yml' | ||
)}, but this version of Tool Kit can only load v${s.code( | ||
CURRENT_RC_FILE_VERSION.toString() | ||
)}. please update this plugin.` | ||
]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought: Some assisting documentation to add as part of the major release to explain why this was done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep. documentation (including a migration guide) will be coming later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea!
8b7f3a4
to
f685467
Compare
f685467
to
a49c1aa
Compare
…atible-well-sort-of Even more backwards compatible (well sort of)
version
field to.toolkitrc
this should provide users with more actionable error messaging if they have outdated plugins, instead of trying to load an old toolkitrc expecting the current structure and which will probably throw some
cannot read property of undefined
error at some point