-
Notifications
You must be signed in to change notification settings - Fork 266
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
Some Selection Extension Properties should be nullable #35
Comments
Ah, thanks a lot! I knew about this, but actually used a workaround in my apps instead of fixing it for some strange reason :) |
Haha I do that too. I tend to cope with small uninteresting problems and procrastinate on fixing them... |
Yeah, good thing we don't procrastinate on the same things :) haha Did you add this change or should I do it? |
Ah forgot about this one. I'll do it today. |
Doing this right now. What is the status of the release? |
Okay done. I'll go ahead and merge. |
Nice! I'll get in some changes to the logging support and documentat that, other than that I think I'm done. What about you? |
Oh, and thanks for all the hard work lately, you've put in a lot of time and effort. Really appreciate it! |
By the way, I reverted the T? type in the |
Got it. That makes sense. |
No problem! Glad to help and I think that's it. I may go through documentation later and add more stuff. I already added example for menus to builders section. |
Perfect! I'll release tonight :) |
Documenting another item that I will fix this weekend. Some of the selection extension properties should be nullable. For example,
Nodes.kt
has some controls with aselectedItem
orselectedValue
property that could be null.To avoid nullability issues, they should be this. I'll do a sweep later to ensure nullable extension properties are indeed nullable.
The text was updated successfully, but these errors were encountered: