-
Notifications
You must be signed in to change notification settings - Fork 245
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
minor: regenerate JSON files #1335
Conversation
Looks like this is related to DRIVERS-1707 cc @Neilshweky @DmitryLukyanov |
@@ -54,7 +47,14 @@ | |||
"commandFailedEvent", | |||
"connectionCheckedOutEvent", | |||
"connectionCheckedInEvent" | |||
] | |||
], |
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.
some minor formatting fix was applied yesterday, but I would not expect such change in order..
"name": "find", | ||
"object": "collection", | ||
"arguments": { | ||
"filter": { |
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.
I don't understand why this change was applied, but probably it's not a big deal
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.
js-yaml
does not inline non-empty objects. By default, keys within an object appear indented on their own line between the opening and closing braces. Likewise for array elements.
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.
Looks like no real changes, so LGTM
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.
LGTM
I am not sure why, but when I regenerated files after making some changes in #1324 these ones changed. Seems like they had not been properly regenerated for whatever reason and the GitHub Action checking the files did not pick it up.