-
Notifications
You must be signed in to change notification settings - Fork 41
Feature/svelte portal 301 #302
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
Conversation
…tion for the new prop, updated how we apply popper.js so that it uses the default rendering system rather than popper.js by default
for more information, see https://pre-commit.ci
Hey @janosh just following up on this : ) hope you like it |
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.
thanks for this PR! 👍
two comments below and we definitely need a unit test for this new prop
@@ -48,14 +48,17 @@ | |||
"rehype-slug": "^6.0.0", | |||
"svelte-check": "^4.0.5", | |||
"svelte-multiselect": "^10.3.0", | |||
"svelte-popperjs": "^1.3.2", |
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.
https://github.com/bryanmylee/svelte-popperjs looks to be unmaintained (last commit 2 years ago) and i think i read that the next major Svelte release is expected to break backward compatibility with Svelte 4. so adding this dependency could become an anchor to Svelte 5 in the future. let's try to minimize the number of new packages added for this feature
@@ -423,6 +423,11 @@ Full list of props/bindable variables for this component. The `Option` type you | |||
|
|||
If `maxSelect={1}`, `value` will be the single item in `selected` (or `null` if `selected` is empty). If `maxSelect != 1`, `maxSelect` and `selected` are equal. Warning: Setting `value` does not rendered state on initial mount, meaning `bind:value` will update local variable `value` whenever internal component state changes but passing a `value` when component first mounts won't be reflected in UI. This is because the source of truth for rendering is `bind:selected`. `selected` is reactive to `value` internally but only on reassignment from initial value. Suggestions for better solutions than [#249](https://github.com/janosh/svelte-multiselect/issues/249) welcome! | |||
|
|||
1. ```ts | |||
fixed: boolean | null = false |
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.
what's the purpose of allowing null
here?
also, can we find a more descriptive name than fixed
. let's call it overflowParent: hidden | visible = visible
or something like that
closing in favor of #306. thanks again for the feature proposal and this first implementation! 👍 |
Closes #301 .
Summary of major changes
fixed
Notes
npm run package && npm run dev
had to run these commands after every change, not sure why but it got the job done