Skip to content

GeoBoundingBox BoundingBox can no longer accept coordinates as params #8464

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

Open
niemyjski opened this issue Feb 28, 2025 · 1 comment
Open
Labels
8.x Relates to a 8.x client version Category: Feature

Comments

@niemyjski
Copy link
Contributor

Is your feature request related to a problem? Please describe.

In nest you could do something like this q.GeoBoundingBox( m => m.Field(p => p.Field3).BoundingBox( "51.5032520,-0.1278990", "51.5032520,-0.1278990"))));

Describe the solution you'd like
It's not clear what options you need on the bounding box without really digging into the code and then changing all the arguments.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@niemyjski niemyjski changed the title GeoBoundingBox BoundingBox can no longer accept cordinates as params GeoBoundingBox BoundingBox can no longer accept coordinates as params Feb 28, 2025
@flobernd
Copy link
Member

flobernd commented Mar 7, 2025

Hey @niemyjski , I think that's the same root cause as in #7812 (no descriptors are generated for union types).

This should be available again after my descriptor rework 🙂

@flobernd flobernd added the 8.x Relates to a 8.x client version label Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.x Relates to a 8.x client version Category: Feature
Projects
None yet
Development

No branches or pull requests

2 participants