Today I found out that CDO has removed the onRecordEvent() function from the toolbox:

This change apparently happened last week, and nobody was notified beforehand that it would be removed and programs using it would have altered functionality. Why did they removed one of the most useful commands in App Lab? I can only think of two possibilities:

  1. Something changed with how data storage works so that a live update function is no longer practical. This doesn't really make sense, since it worked fine before.
  2. This is another attempt by CDO to remove chats. It's possible, but also kind of pointless since chats can work just fine using timedLoop() and key values.

Either way, the code for it has been completely removed. Projects using it won't crash, but they will throw a red flag and any code nested inside an onRecordEvent() will not run. If anyone has a workaround please let me know!

    Binary_Coder For some reason Code.org is completely rigging everything in the data tab, its very stupid. I'm pretty sure this is an effort to get rid of chats by making everyone else's life miserable since you have to use data.

      Binary_Coder well i took the time to read the response.... the function is getting deprecated in the back end so it wouldn't work later on anyways even if the top level function still exsisted

      even though it may make sense for more advanced users to have it, it would require the back end to continue supporting it, and since CDO is mainly for the curriculum there's not really much point in keeping it besides actually having functional data listeners which are very useful since it puts less stress on the read & write calls on the database buuut most of the people who are maintaining the repo are more focused on other stuff so it's not like you can really blame them

        Lol.
        CDO is working on clearing all the chats with an AI bot that I suggested.
        Hehe

        Binary_Coder
        Yeah, good thing I didn’t use that function.
        Also, are they planning to remove other data functions?

        [WUT] Adam
        They really think that it’s all your fault?

              LGM_Productions I don't think that's what he meant. I think he was just saying how the number of projects from 2022 that use onRecordEvent is even more significant since some of them are remixes of my apps.

              Also, from what I can tell, they're moving over to MySQL, and onRecordEvent was a feature built-in with Firebase. They're moving for cost reasons, and apparently since WebSockets are too costly, they're not recreating the feature.

                  [WUT] Adam hmm.... does that mean i'm gonna have to update my cdo-sync project again? i assume so and I'm probs gonna have to update there package as well to work with previous modifications i made, NVM they are still planning on using firebase but they depricated the listener due to potential costs though i think they still plan on using it for storage for the forseeable future

                  yknow what would be useful though is populateKeyValues & populateTables of which should be a no brainer to implement and will save read and write calls to the database to stop it from rate limiting of which i found in there package that they aren't using of which i made it super easy to sync projects, in fact there is such thing as a perfect remix using my tool since you won't be losing any of the data from the project

                    Chat