-
Notifications
You must be signed in to change notification settings - Fork 26
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
AddressNL autocomplete: handle empty response #4430
Comments
vaszig
added a commit
that referenced
this issue
Jun 25, 2024
When we had no data from the API call, secretStreetCity was not created and was an empty str, so it couldn't validate with the one that was created in the backend validation. Now, we create one even when no data is returned and this makes backend validation possible.
9 tasks
vaszig
added a commit
that referenced
this issue
Jun 25, 2024
When we had no data from the API call, secretStreetCity was not created and was an empty str, so it couldn't validate with the one that was created in the backend validation. Now, we create one even when no data is returned and this makes backend validation possible.
sergei-maertens
added a commit
that referenced
this issue
Jun 26, 2024
…bag-response-in-addressnl-autocomplete [#4430] Handle empty response from bag client
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we make the call to the API in order to retrieve the
city
and thestreetName
we may encounter an error, so we will get no data.Now, the validate API call to the backend returns an empty response if this is the case, so we have a backend validation error concerning the
secretCityStreename
field. This could possibly be solved by returning empty string instead of an empty response and this could still calculate a secret.The text was updated successfully, but these errors were encountered: