So, to keep everything as simple and clear as possible, when using the method :GetSortedAsync() on an OrderedDataStore, the Roblox Engine thinks that it returns an Instance as shown here:
Expected behavior
However, it should return a DataStorePages object, as shown here:
Therefore, a quick fix should just be a quick update on the return type.
It would avoid confusions with the AutoComplete:
Usually action will take longer for non-critical issues, it isn’t like :GetSortedAsync is broken. This bug is “cosmetic” and has no behavioral effect, thus it has lower priority compared to more serious ones, which will be worked on with more immediacy.
Also, there hasn’t been a “We’ve received your report and filed a ticket” reply, so this bug might not have been filtered through to the correct team yet. They did also recently open Bug Reports to everybody, so there’s probably a larger backlog in that area.
it has behavioral effect. --!strict mode wouldnt work properly.
Type checking warnings do not influence runtime behaviour. You could have a warning on every single line, but no actual errors.
I can understand that Roblox has more urgent issues. However, with thousands of employees and 0 other opened Engine Bugs report, I don’t think that they’re “too busy” fixing other things.
Not every single one is working on the Engine, Roblox is an entire platform after all. Game Engines are already massive endeavors, and, eventually, people start to spread thin when you have so many different specialties to tend to.
… What? You can literally view the reports in the #bug-reports:engine-bugs category and see that 99% of the hundreds of recent ones are marked as “Open”, and still under progress of being resolved. You have to wait in line like the rest, especially when your bug doesn’t have a high impact, even if it’s easy to fix, because everything takes at least a little bit of time, and there are hundreds of other bugs that they need to prioritize, along with implementing new features.
Saying that they “aren’t doing their job” is simply oblivious.
EDIT: Also, this should be under #bug-reports:studio-bugs. It would be funny if that has contributed to the lack of staff response (I would assume it doesn’t), but I just noticed.
Thanks for the report. This issue has been fixed.
