-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comma escape #1191
base: main
Are you sure you want to change the base?
Comma escape #1191
Conversation
@@ -86,6 +86,7 @@ | |||
notification.job_id, | |||
notification.job_row_number, | |||
) | |||
print(hilite(f"recipient: {recipient}")) |
Check failure
Code scanning / CodeQL
Clear-text logging of sensitive information High
sensitive data (private)
@@ -108,6 +109,7 @@ | |||
"sender": notification.reply_to_text, | |||
"international": notification.international, | |||
} | |||
print(hilite(f"send_sms_kwargs: {send_sms_kwargs}")) |
Check failure
Code scanning / CodeQL
Clear-text logging of sensitive information High
sensitive data (private)
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 believe this is okay to keep here for the moment for debugging purposes.
Stack trace with the current error I am stuck on.
|
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 a job for isort
to make this clear up in the tests. Otherwise, LGTM
Description
We are trying to find a way to figure out the comma issue for csv's/one-offs when a user has extra commas inside of fields. Added debug statements to help see what's happening in
extract_personalisation
.I've added more debug statements to try and figure out where the issue is coming from in the api. The value sent from the front-end during a one-off send is wrapped in quotes like so "July 23, 2024" and everything seems to be correct in the debug statements except for the "To" number. I think the phone number is still being swapped for one of the other values somewhere in the create_job process.
TODO (optional)
Security Considerations