Closed stockiNail closed 2 years ago
Not sure what the reason was behind re exporting string as another type without actually doing something with it but I think this is better and more type safe that what it was before
@LeeLenaleee we have tried in the past that format but it seems is not compatible with some TS version... I'm looking for the comment in a PR
Guess it is anything lower as 4.1 @stockiNail. Because that is when it was released: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-1.html
But since it is a V2 release I guess we can call it a breaking change and require at least TS version 4.1 since 4.1 is already 2 years old
EDIT: Guess we also need to put a note in the migration guide then
Guess it is anything lower as 4.1 @stockiNail. Because that is when it was released: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-1.html
But since it is a V2 release I guess we can call it a breaking change and require at least TS version 4.1 since 4.1 is already 2 years old
Could make sense for me. If all agree, I need to change this PR in order to
Let me know. As said, for me it's fine.
This PR is changing the types definitions in order to:
AnnotationCoordinates
because adds the options inCoreAnnotationOptions
AnnotationPluginCommonOptions
and changescommon
option defintion to accept a types annotation options