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

return an empty result when geolocation data is not found #341

Merged
merged 1 commit into from
Jan 3, 2024

Conversation

joeshaw
Copy link
Member

@joeshaw joeshaw commented Dec 19, 2023

This matches the Fastly Compute behavior.

As a result, we don't need the GeolocationError type anymore and this
commit also removes it.

Fixes #339.

This matches the Fastly Compute behavior.

As a result, we don't need the `GeolocationError` type anymore and this
commit also removes it.

Fixes #339.
Copy link
Contributor

@JakeChampion JakeChampion left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@joeshaw joeshaw merged commit c588597 into main Jan 3, 2024
7 checks passed
@joeshaw joeshaw deleted the joeshaw/geo-not-found-empty branch January 3, 2024 15:16
cmckendry pushed a commit to 1stdibs/Viceroy that referenced this pull request Feb 8, 2024
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.

Geo lookup returns FastlyStatus::None when not found, which is different from Compute
2 participants