[Resolver] model location.search in redux#76140
Conversation
6f44894 to
62a06bb
Compare
There was a problem hiding this comment.
This file will have the logic for getting values out of (and constructing new) URLSearchParams
There was a problem hiding this comment.
This action isn't specific to data at all so I'm going to move it to the top level Resolver actions file.
There was a problem hiding this comment.
use this to get the query string parameters used by the panel
There was a problem hiding this comment.
This function was added. the rest of the changes (except for import statements) are white space.
There was a problem hiding this comment.
use the selector to get the panel query params now
There was a problem hiding this comment.
renamed useResolverQueryParams to this. it no longer returns the query params.
There was a problem hiding this comment.
dispatch this action any time the location.search changes.
There was a problem hiding this comment.
Having this action fire whenever location.search changes seems sort of overkill, why not just when the relevant params change?
There was a problem hiding this comment.
The app will need to read the entire query string. For example, we might need to show a link that causes our panel to open. In that case we'll want the link to include all query string values (not just ones relevant to this Resolver instance.)
kqualters-elastic
left a comment
There was a problem hiding this comment.
Since I had more or less the same logic just in a few different places, LGTM 👍 looks great to me!
Begin reading `location.search` via redux so that all parts of the app share a single source of truth about it
ca58e92 to
aee1ee4
Compare
| * you may not use this file except in compliance with the Elastic License. | ||
| */ | ||
|
|
||
| import { i18n } from '@kbn/i18n'; |
💚 Build SucceededBuild metrics@kbn/optimizer bundle module count
async chunks size
distributable file count
History
To update your PR or re-run it, just comment with: |
Read location.search from the redux store instead of a hook so that the entire view has a single (synchronized) source of truth. Also, no longer pass `pushToQueryParams` function to various components.
…s-for-710 * 'master' of github.com:elastic/kibana: (43 commits) [APM] Chart units don't update when toggling the chart legends (elastic#74931) [ILM] Add support for frozen phase in UI (elastic#75968) Hides advanced json for count metric (elastic#74636) add client-side feature usage API (elastic#75486) [Maps] add drilldown support map embeddable (elastic#75598) [Enterprise Search] Request handler refactors/enhancements + update existing routes to use shared handler (elastic#76106) [Resolver] model `location.search` in redux (elastic#76140) [APM] Prevent imports of public in server code (elastic#75979) fix eslint issue skip flaky suite (elastic#76223) [APM] Transaction duration anomaly alerting integration (elastic#75719) [Transforms] Avoid using "Are you sure" (elastic#75932) [Security Solution][Exceptions] - Fix bug of alerts not updating after closure from exceptions modal (elastic#76145) [plugin-helpers] improve 3rd party KP plugin support (elastic#75019) [docs/getting-started] link to yarn v1 specifically (elastic#76169) [Security_Solution][Resolver] Resolver loading and error state (elastic#75600) Fixes App Search documentation links (elastic#76133) Fix alerts unable to create / update when the name has trailing whitepace(s) (elastic#76079) [Resolver] Fix useSelector usage (elastic#76129) [Enterprise Search] Migrate util and components from ent-search (elastic#76051) ... # Conflicts: # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/components/data_tier_allocation/node_allocation.tsx # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/edit_policy.tsx # x-pack/plugins/index_lifecycle_management/public/application/services/policies/types.ts # x-pack/plugins/index_lifecycle_management/public/application/services/policies/warm_phase.ts
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Read location.search from the redux store instead of a hook so that the entire view has a single (synchronized) source of truth. Also, no longer pass `pushToQueryParams` function to various components. Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>


Read
location.searchfrom the redux store instead of a hook so that the entire view has a single (synchronized) source of truth.Still works:

Still works in the test app as well:

Checklist
For maintainers