-
Notifications
You must be signed in to change notification settings - Fork 30
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
3.10: Query rules #413
Conversation
arangodb-net-standard/AqlFunctionApi/Models/GetQueryRulesResponseItem.cs
Outdated
Show resolved
Hide resolved
arangodb-net-standard/AqlFunctionApi/Models/GetQueryRulesResponseFlags.cs
Outdated
Show resolved
Hide resolved
@DiscoPYF thanks for your review. I've made the relevant changes and looking forward to your approval. |
[Fact] | ||
public async Task GetQueryRulesAsync_ShouldSucceed() | ||
{ | ||
if (_fixture.VersionMajor >= 3 && _fixture.VersionMinor >= 10) |
There was a problem hiding this comment.
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.
See https://github.com/arangodb/docs/blob/main/3.10/release-notes-api-changes310.md#optimizer-rules-for-aql-queries