No release notes for this holiday week! Though if you havenβt noticed yet, we pushed an update to our docs (especially our API docs) and I hope you can take a gander when you can.
Leave some feedback if youβd like and have a great week. Stay safe and enjoy time with your friends and family
I mentioned this in signalβs feedback server, but itβd be nice if deprecated functions & properties had strikethrough on them so itβs easier to see at a glance that theyβre depreacted.
Why are there two buttons for opening the sections?
I can just click the classes section to open it, I donβt need a big button saying βSee classesβ to open a section that I couldβve just opened using the drop down that is on the left.
I donβt know if it was always like that but was rather strange design
Thatβs a good point. Weβve had a discussion re: surfacing nillable types with the team before, and Iβll make sure to bring it up again. Itβs exposed in the yaml as well, so it seems like an easy lift, unless Iβm missing something.
Itβs not intuitive to click the Learn button on the side to see the other sections. I had a lot of trouble intuitively navigating outside of the engine API reference to something else like cloud API reference, and it felt very siloed off as a result.
Iβll double check on this - I know we were thinking on how to better show (or not show) deprecated endpoints. I think strikethroughs have some initial issues wrt readability and accessibility (maybe localization as well?) but Iβll make sure we look into the best way to flag.