-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Avoid clashing class_ slot in List parameter #456
Conversation
This is probably the real issue: #97 |
The tests are passing and this is a fairly simple workaround for #97. Even then, I would argue there is a difference between |
I'd agree it justifies a different slot but as you say this is really a workaround for a deeper issue. Also not sure about |
Happy to rename to |
Maybe @jbednar has a better suggestion for the naming. I'd at least like to see |
#97 does need addressing, but I agree it's a much larger job than putting in a workaround here, so we should do both. Regarding this specific workaround, I agree that the type for the items in a collection is semantically different than the type for a selector, so having a separate slot is very reasonable. The name |
@jbednar @philippjfr Happy with this workaround fix for now? |
@philippjfr I see you've merged but what about Jim's point about pickling and |
Missed that :/ |
Avoid clashing class_ slot in List parameter (holoviz#456)
Here is one way to address #455, namely to make sure the
List
parameter does not use the sameclass_
slot asClassSelector
(I called itlist_class
for now instead).Generally, I'm not sure why parameters inherit previous slot values at all (when they have a value of None) tbh...