Skip to content

[client] Breaking change - Rename @Client.Import(types=...) to @Client.Import(value=...). That is, rename types -> value #557

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

Merged
merged 1 commit into from
Jan 27, 2025

Conversation

SentryMan
Copy link
Collaborator

@SentryMan SentryMan commented Jan 27, 2025

Now can do @Client.Import(CustomType.class)


This is a breaking change

From:

@Client.Import(types = OtherApi.class)

To:

@Client.Import(value = OtherApi.class)

... and because it is value it can be now written as:

@Client.Import(OtherApi.class)

@SentryMan SentryMan requested a review from rbygrave January 27, 2025 05:19
@SentryMan SentryMan self-assigned this Jan 27, 2025
@SentryMan SentryMan enabled auto-merge (squash) January 27, 2025 05:20
@SentryMan
Copy link
Collaborator Author

also shouldn't we be doing 3.0-RCs?

@SentryMan SentryMan added this to the 3.0 milestone Jan 27, 2025
@rbygrave rbygrave changed the title [client] Rename Import types member [client] Breaking change - Rename @Client.Import(types=...) to @Client.Import(value=...). That is, rename types -> value Jan 27, 2025
@SentryMan SentryMan merged commit 6c734c0 into avaje:master Jan 27, 2025
6 checks passed
@SentryMan SentryMan deleted the client-import branch January 27, 2025 13:40
@rbygrave
Copy link
Contributor

also shouldn't we be doing 3.0-RCs?

Yes, these 2.9-RCs are really 3.0-RCs. We started on 2.9.x and I didn't change it ... but maybe we should.

@SentryMan
Copy link
Collaborator Author

time for 3.0-RC1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants