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

Update response for schedule list #351

Merged
merged 3 commits into from
Jul 19, 2024
Merged

Conversation

imnutz
Copy link
Contributor

@imnutz imnutz commented Jul 17, 2024

Add executing_user_id and description to the response

@imnutz imnutz requested a review from tung-vu-td July 17, 2024 01:04
Copy link
Contributor

@tung-vu-td tung-vu-td left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines 216 to 217
", engineVersion='" + engineVersion + '\'' +
", executingUserid='" + executingUserId + '\'' +
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
", engineVersion='" + engineVersion + '\'' +
", executingUserid='" + executingUserId + '\'' +
", engineVersion=" + engineVersion +
", executingUserId=" + executingUserId +

NIT: Single quotes aren't necessary.

@imnutz imnutz requested a review from a team July 18, 2024 09:11
Copy link

@ylzen ylzen left a comment

Choose a reason for hiding this comment

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

Reviewed for Data Exfiltrations.

Please address existing review comments.

@imnutz imnutz force-pushed the update_response_for_schedule_list branch from 2b951b3 to 6eb1022 Compare July 19, 2024 01:37
@imnutz imnutz merged commit 3e0e2c4 into master Jul 19, 2024
7 checks passed
@imnutz imnutz deleted the update_response_for_schedule_list branch July 19, 2024 01:57
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.

4 participants