-
Notifications
You must be signed in to change notification settings - Fork 7
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
2331 hd aln 27011 no accepted #2380
Conversation
…ed jsonnet formatting
…' into 2331-hd-aln-27011-no-accepted
Terraform plan for dev No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #266 |
Terraform plan for meta No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #266 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 58cbfcc |
We were passing cells with just spaces through, which are an invisible kind of error for users. We now strip() strings.
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.
Tested locally and was able to get the error table listed in the PR description.
Left one comment inline, but it's not a blocker for merging.
data_dict = error.schema | ||
# Check if the input data is in the format { ... 'not': {'required': ['field_name']}} | ||
if "not" in data_dict and "required" in data_dict["not"]: | ||
field_name = data_dict["not"]["required"][0] |
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.
Are there any future cases where we'll have a list of not-required entries? It doesn't look like there are any cases where we have more than one field name in {... 'not': {'required': [...]
, but we might want to keep this in mind just in case.
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.
We could be aggressive here and update the logic to account for a list of not required
fields
Description
See #2331
After investigation, it turned out that the application returns erroneous error reports due to the validation logic that is unable to properly capture the invalid field names from the error schema.
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)PR checklist: reviewers
make docker-clean; make docker-first-run && docker compose up
; then rundocker compose exec web /bin/bash -c "python manage.py test"
The larger the PR, the stricter we should be about these points.