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

3.10: Query rules #413

Merged
merged 5 commits into from
Oct 11, 2022
Merged

3.10: Query rules #413

merged 5 commits into from
Oct 11, 2022

Conversation

@tjoubert tjoubert requested a review from DiscoPYF August 29, 2022 08:57
@tjoubert tjoubert self-assigned this Aug 29, 2022
@tjoubert tjoubert requested a review from DiscoPYF October 5, 2022 17:22
@tjoubert
Copy link
Contributor Author

tjoubert commented Oct 5, 2022

@DiscoPYF thanks for your review. I've made the relevant changes and looking forward to your approval.

@tjoubert tjoubert merged commit 5bdb794 into master Oct 11, 2022
@tjoubert tjoubert deleted the feature3.10/DE-341-query-rules branch October 11, 2022 06:25
[Fact]
public async Task GetQueryRulesAsync_ShouldSucceed()
{
if (_fixture.VersionMajor >= 3 && _fixture.VersionMinor >= 10)
Copy link
Collaborator

@DiscoPYF DiscoPYF Oct 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we implement this check using the ServerVersion Trait like here?

[Fact]
[Trait("ServerVersion", "3_10_PLUS")]
public async Task GetQueryRulesAsync_ShouldSucceed() { }

Or was this meant to be a new approach?

Both approaches have pros and cons. The Trait one is more visible, but a bit cumbersome as we need to update the test command in the config file for each version.

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