Skip to content
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

Api: Implement ConditionExpression API. #73

Merged
merged 1 commit into from
Sep 4, 2023

Conversation

Jeffset
Copy link
Contributor

@Jeffset Jeffset commented Aug 29, 2023

This is in a way Conditions API 2.0, which
we are able to introduce as the "legacy" API is not stable yet.

This realizes the full potential of the support for the arbitrary
boolean expressions, implemented in #67.

Legacy is API is left fully intact and working, the new
API can be used besides the old.

Closes #65.

@Jeffset Jeffset marked this pull request as ready for review August 29, 2023 14:07
@Jeffset Jeffset marked this pull request as draft August 29, 2023 14:07
@Jeffset Jeffset requested a review from byar August 29, 2023 14:07
@Jeffset Jeffset marked this pull request as ready for review August 29, 2023 14:08
@Jeffset Jeffset linked an issue Aug 29, 2023 that may be closed by this pull request
This is in a way Conditions API 2.0, which
 we are able to introduce as the "legacy" API is not stable yet.

This realizes the full potential of the support for the arbitrary
 boolean expressions, implemented in #67.

Legacy is API is left fully intact and working, the new
 API can be used besides the old.

Closes #65.
@Jeffset Jeffset merged commit e978e03 into main-1.4.0 Sep 4, 2023
1 check passed
@Jeffset Jeffset deleted the wp/condition-expressions branch September 4, 2023 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide more convenient alternative to @Condition-like annotations
2 participants