Skip to content

Conversation

@guimachiavelli
Copy link
Member

@guimachiavelli guimachiavelli commented Sep 6, 2022

Closes #1851

This is not strictly necessary as we don't usually go into too much detail in the errors page, nor do we describe variant errors.

Still, I took the update as an opportunity to add a bit more info to the description in hopes we can save users a click to the dedicated guide.

@guimachiavelli guimachiavelli added this to the v0.29 milestone Sep 6, 2022
Copy link
Member

@Kerollmops Kerollmops left a comment

Choose a reason for hiding this comment

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

Looks good to me!

Copy link
Contributor

@maryamsulemani97 maryamsulemani97 left a comment

Choose a reason for hiding this comment

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

💀

@guimachiavelli guimachiavelli linked an issue Sep 28, 2022 that may be closed by this pull request
@guimachiavelli
Copy link
Member Author

bors merge

@bors
Copy link
Contributor

bors bot commented Sep 29, 2022

@bors bors bot merged commit 20f15d8 into v0.29 Sep 29, 2022
@bors bors bot deleted the v0.29-invalid-geo-field branch September 29, 2022 13:52
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.

v0.29: Changes to invalid_geo_field error

4 participants