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 
naahchos
When will the API documentation be updated to show nillable return types?
(Note that it does say it can be nil in the description, but it really should be Instance? here imo)
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 don’t know if it was always like that but was rather strange design
I probably won’t notice the docs update as I rarely use them but you have a great week and enjoy some time with friends and family as well 
Was wondering why production didn’t get an update today… then realized the engineers must be enjoying thanksgiving. Have a fun holiday.
Those big buttons have always been there.
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.
with some hope we finna get it
Why not just make it a toggle like it was before, with deprecated being hidden by default?
