-
-
Notifications
You must be signed in to change notification settings - Fork 103
(WIP) Use define-deprecated-alias
for legacy aliases
#1460
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
base: master
Are you sure you want to change the base?
Conversation
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.
Resyntax analyzed 2 files in this pull request and has added suggestions.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
Resyntax analyzed 2 files in this pull request and found no issues.
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.
Resyntax analyzed 2 files in this pull request and found no issues.
@samth These test failures confound me. Any idea what's going on here?
|
That's some of the most fragile code in TR. Is that test using the old alias or the new name? |
This is a (very) work-in-progress pull request to use the new
define-deprecated-alias
form to define the various aliases listed in Legacy Forms. This will allow Resyntax to automatically migrate users of these forms to their recommended replacements.