Skip to content

Conversation

@hansmannj
Copy link
Member

@hansmannj hansmannj commented Jun 17, 2025

Since the API now handles the geo+json content type issue, we should remove the preprocessor from the browser's config

Since the API now handles the geo+json content type issue, we
should remove the preprocessor from the browser0s config
@sami-nouidri-swisstopo
Copy link

I tried before yesterday's deployment and today again, but it seems without the hook the search just doesn't show up :
image

Copy link

@ltshb ltshb left a comment

Choose a reason for hiding this comment

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

I don't understand here, @sami-nouidri-swisstopo added this very recently and now you remove it ? Did you try it does it work without it ? But now we also downgraded STAC to v1.37...

@hansmannj
Copy link
Member Author

hansmannj commented Jun 19, 2025

Since we adapted the API so that the search endpoints reply with a geo+json if this is explicitly requested via the accept header, I thought, that would make the preprocessing obsolete, but obviously it doesn't.
Maybe I'll use this PR to add a comment on the preprocessor, so that we know someday in future, why we have it and when we can remove it.

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.

4 participants