-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat(hub-common): hubSearchEvents switch to new POST events search route #1787
feat(hub-common): hubSearchEvents switch to new POST events search route #1787
Conversation
bf96ac7
to
fa81971
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for making these updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I pulled this branch into my opendata-ui sandbox and verified things are working as expected. Nj!
One minor request, would you remind removing this line as userId
is not a supported filter.
affects: @esri/hub-common
affects: @esri/hub-common
affects: @esri/hub-common
affects: @esri/hub-common
affects: @esri/hub-common
affects: @esri/hub-common
98a0d14
to
945a1d1
Compare
# @esri/hub-common [15.26.0](https://github.com/Esri/hub.js/compare/@esri/[email protected]...@esri/[email protected]) (2025-01-31) ### Features * **hub-common:** hubSearchEvents switch to new POST events search route ([#1787](#1787)) ([8fbb944](8fbb944))
affects: @esri/hub-common
https://devtopia.esri.com/dc/hub/issues/12274
Description: In
hubSearchEvents
, swapgetEvents
withsearchEvents
. This function points to the new POST /events/search route. Update the process filter and options functions for the new interface (remove parsing to string)Instructions for testing:
Closes Issues: # (if appropriate)
Updated meaningful TSDoc to methods including Parameters and Returns, see Documentation Guide
used semantic commit messages
PR title follows semantic commit format (CRITICAL if the title is not in a semantic format, the release automation will not run!)
updated
peerDependencies
as needed. CRITICAL our automated release system can not be counted on to updatepeerDependencies
so we must do it manually in our PRs when needed. See the updating peerDependencies section of the release instructions for more details.