Modified validators in few files according to new ValidateObject

[Abhishek-Punhani]

I have modified the validators function in three Vue files to incorporate the new validateObject function.

Reference Issue #8903

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.18.0a0.dev0_git.373.g97227d37.pex
Windows Installer (EXE)	kolibri-0.18.0a0.dev0+git.373.g97227d37-windows-setup-unsigned.exe
Debian Package	kolibri_0.18.0a0.dev0+git.373.g97227d37-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.18.0a0.dev0+git.373.g97227d37.dmg
Android Package (APK)	kolibri-0.18.0a0.dev0+git.373.g97227d37-0.1.4-debug.apk
Raspberry Pi Image	kolibri-pi-image-0.18.0a0.dev0+git.373.g97227d37.zip
TAR file	kolibri-0.18.0a0.dev0+git.373.g97227d37.tar.gz
WHL file	kolibri-0.18.0a0.dev0+git.373.g97227d37-py2.py3-none-any.whl

[nucleogenesis]

This looks good to me and addresses the particular instances noted in the linked issue.

It gets me wondering if it'd be worth codifying these pseudo type definitions for things like a ContentNode similar to this one I did for quiz-related data types. Would be nice to be able to say validator(val) { validateObject(ContentNodeSpec) }.

Maybe I will create an issue for that for the future :)

Thanks for this @Abhishek-Punhani !

[Abhishek-Punhani]

@nucleogenesis Thank you for the feedback! I agree that codifying pseudo-type definitions for objects like ContentNode is a fantastic idea—it would greatly enhance consistency and readability throughout the codebase. If an issue is created for this, I’d be happy to contribute to its implementation.
Please let me know if there’s anything else you’d like me to address or adjust. Are there any additional steps required before this can be merged?