[C-1431] Clean the console warnings appearing in the local dev environment

[skwowet]

Describe the problem

I usually try debugging data related things by console logging in the frontend to ensure what's been sent as response from the backend, but currently doing the same with our code base is kinda feels difficult.

Every time when I open a page in the platform on local dev environment shoots like 50+ type and other warnings.

Here's the screenshot for reference, check the developer console below 👇

Describe the improvement

We should consider cleaning/resolving those warning, and it will be easy for people like me who uses console logs a lot.

Additional Context

Console logging things aren't advised, though, but still comes in handy 😛 Please do read the articles below to learn more!

• Please stop using console logs for debugging - Better Programming
• Stop using console logs - Ben Lmsc, Founder of Brant

_C-1431

[skwowet]

I will be happy to take up the issue, let me know!

[jonathimer]

would be awesome if you could tackle this! 😎

[skwowet]

@jonathimer cool, thanks for assigning me. I will work on this once I fix issue #755 🐳

[skwowet]

I've begun working on this issue and will soon open a PR for it 🏌🏻‍♂️

[joanreyero]

Hey @yeganathan18! Do you need any more help from our side for this? 😊

[skwowet]

@joanreyero Oops, my bad! I actually started working on that issue but got sidetracked and, TBH, totally forgot about it later on. 🤦🏻‍♂️ I ended up focusing on other issues and fixed them instead.

Right now, I'm taking a study break 'cause of my university exams, but once I'm back in action, I'll jump right back into the issue. Meanwhile, if anyone's interested in picking up where I left off, I'm more than happy to help! 🔧

[peoray]

Picking this up. @yeganathan18 need more context especially as you had started work on it :)

[skwowet]

@peoray Thanks for picking this up! 🍻 I missed this while working on other critical tasks

Some warnings were already fixed I believe but in most cases it's just updating things like custom-class --> class here since it is going to be deprecated in version 2.3.0.

The challenge I was facing when working on the issue was locating the components that need the fix, also requires lots of granular changes in code base.

Please let me know if you require any help along the way 😄

[peoray]

thank you. that's a good start.

[skwowet]

@peoray need any more help, buddy? 🙂

[peoray]

@yeganathan18 plenty of issues to resolve, each page comes with its own errors lol. we can pair to take a look. Some errors are constant though like the only-child node error and some deprecation warning errors too