-
Notifications
You must be signed in to change notification settings - Fork 1
fix(FSADT1-1650): fixing order of query #273
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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mamartinezmejia
approved these changes
Dec 2, 2024
|
|
- Line continuation have incorrect indentation level, expected level should be 4. - Line is longer than 100 characters (found 110).
|
mamartinezmejia
approved these changes
Dec 2, 2024
Your Pull Request code is being promoted! Please follow the link below. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Query sorted in a weird way, changed to use a score system
Type of change
How Has This Been Tested?
Checklist
Further comments
Thanks for the PR!
Any successful deployments (not always required) will be available below.
API available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow