Closed kandrelczyk closed 1 day ago
I didn't add keyboard functionality to the auto complete. I did some testing and it can be done using AutoCompleteInjection as a proxy between AutoComplete and children but I'm not sure if it's the right way to do it.
We can investigate how FluentUI does it.
https://github.com/microsoft/autocomplete-search-box - that's all I found, I don't see auto complete component on the react.fluentui.dev
So they pass options as a list and use optional custom renderers. What's the purpose of changing this to accept children? What additional features would this allow us to add?
https://github.com/microsoft/fluentui/blob/master/packages/react/src/components/ComboBox/ComboBox.tsx - no idea how it works. I see the components receiving 'props.options' but I don't know how the
Ok, I added "attr:style" to the table generated from markdown but this branch is still using leptos 0.6 so I can't see the effect. I've seen the fluent branch with leptos 0.7 so I'm assuming it will work there and leave it for now.
no idea how it works. I see the components receiving 'props.options' but I don't know how the children are transformed into an array or IComboBoxOption type.
We can discuss this in Discord.
Thank you for working on this.
Fixed the search.
Light/dark theme selection is now stored in local storage. It looks like it was supposed to be stored in the URL but it wasn't fully implemented.
Added discord button.
Fixed issue with message bar markdown.
Removed options param from auto complete.
I didn't add keyboard functionality to the auto complete. I did some testing and it can be done using AutoCompleteInjection as a proxy between AutoComplete and children but I'm not sure if it's the right way to do it.