-
Notifications
You must be signed in to change notification settings - Fork 105
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
Implement a mechanism for accepting old check-IDs #4942
Comments
The mechanism will be temporary, displaying a message to users: DEPRECATION WARNING: By late-December 2024, FontBakery version 0.13.0 introduced a new naming scheme for the check-IDs. Fontbakery detected usage of old IDs and performed an automatic backwards-compatibility translation for you. This automatic translation will be deprecated in the next major release. Please start using the new check-IDs as documented at |
All reporters are now listing which legacy check-IDs were used on the `--check-id` and `--exclude-checkid` options and instructing the users to update to the new naming scheme, because the old ones will be permanently deprecated in the next major release. (issue fonttools#4942)
All reporters are now listing which legacy check-IDs were used on the `--check-id` and `--exclude-checkid` options and instructing the users to update to the new naming scheme, because the old ones will be permanently deprecated in the next major release. (issue fonttools#4942)
All reporters are now listing which legacy check-IDs were used on the `--check-id` and `--exclude-checkid` options and instructing the users to update to the new naming scheme, because the old ones will be permanently deprecated in the next major release. (issue fonttools#4942)
All reporters are now listing which legacy check-IDs were used on the `--check-id` and `--exclude-checkid` options and instructing the users to update to the new naming scheme, because the old ones will be permanently deprecated in the next major release. (issue #4942)
Based on
Lib/fontbakery/legacy_checkids.py
The text was updated successfully, but these errors were encountered: