feat(#701): Refactor Annotation Properties #739
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR I significantly simplified the work with annotation values.
Now we don't have ugly enums and for each case we have a separate small object that is resposible
only for its own area.
I removed
DirectivesAnnotationProperty
andBytecodeAnnotationProperty
classes since they violate code standards.Closes: #701.
History:
PR-Codex overview
This PR focuses on refactoring the
BytecodeAnnotationProperty
class and related components in theorg.eolang.jeo.representation
package. It introduces new classes for different annotation value types and updates existing logic to utilize these new structures.Detailed summary
BytecodeAnnotationProperty
andDirectivesAnnotationProperty
classes.BytecodePlainAnnotationValue
,BytecodeArrayAnnotationValue
,BytecodeEnumAnnotationValue
, andBytecodeAnnotationAnnotationValue
.XmlAnnotationProperty
to return new bytecode types.annotationProperty
method to use new classes.DirectivesPlainAnnotationValue
,DirectivesEnumAnnotationValue
,DirectivesArrayAnnotationValue
, andDirectivesAnnotationAnnotationValue
.