chore(docs): refactor places-ui-kit example into dedicated components for UI Kit elements #883
Conversation
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
pappkartoni
changed the title
usefulthink
reviewed
Jan 23, 2026
Collaborator
usefulthink
left a comment
usefulthink
left a comment
There was a problem hiding this comment.
Awesome, thanks. Thats exactly the style of API I would imagine for the places ui kit components. A couple of smaller remarks in the code.
examples/places-ui-kit/src/components/basic-place-autocomplete.tsx
Outdated
Show resolved
Hide resolved
Collaborator
|
One more thing, the components can in part be styled using css-variables, should we provide an interface for those as well, so users can style them using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Using dedicated components for the Places UI Kit components
see #878