improve locations page UI by props#299
Merged
zikani03 merged 1 commit intoMay 26, 2026
Merged
Conversation
9 tasks
olewandowski1
requested changes
Feb 11, 2026
Blue-B-code
force-pushed
the
feature-35268
branch
from
0df415f to
cc29d19
Compare
|
vaneck237
approved these changes
Feb 16, 2026
zikani03
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Since SearcherPane an SearcherActionButton are generics components used all over the entire app, in order to improve the TypeLocationsPaper UI in fe-location without impacts in another module, we've set a props Component "ActionButton" to make us able to control the rendering in SearcherPane through modules.
Type of Change
Related Issue(s) / Task(s)
Demo
Upload screenshots/gifs or link to any demo video here.
Checklist