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
{{ message }}
This repository was archived by the owner on Jan 19, 2025. It is now read-only.
After changes to an API we still want to use most of the @boundary annotations.
Desired solution
Migrate the @boundary annotations through a mapping from old api elements to new api elements. If there is not more than one similar api element, and it requires a number, change the target of the annotation.
Otherwise, mark all similar api elements which parameter types are int or float with an unsure (?) @boundary annotation.
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
Create the file package_parser/processing/migration/annotations/_migrate_boundary_annotation.py with a function to migrate an annotation with the related mapping.
See #1125.