Skip to content
This repository was archived by the owner on Jan 19, 2025. It is now read-only.
This repository was archived by the owner on Jan 19, 2025. It is now read-only.

Migrate @boundary annotations #1142

@Aclrian

Description

@Aclrian

Is your feature request related to a problem?

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.

Metadata

Metadata

Assignees

Labels

@boundaryRelated to the @boundary annotationenhancement 💡New feature or requestmigrationMigration of annotation to a new API versionreleasedIncluded in a release

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions