-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Prevent infinity loops errors by validating challengeData #297
fix: Prevent infinity loops errors by validating challengeData #297
Conversation
Good work! It works wonderfully (even without the Nuxt version update). |
@eremia2001 why did you change the |
@Defelo Hey, i had some synching issues thats why .But i am going to revert the changes if its not needed |
@Lauritz-Tieste could you test this again please, so we can merge this? |
Preview deployed to https://ef2fead1.academy-preview.pages.dev (total size: 14M) |
i also tested it once again. it works as before . I apologize for the mess . |
Yeah, everything works! 👍 |
@eremia2001 Du darfst mir sehr gerne auch die Rechnung per Mail stellen - alle Infos dazu hier Danke fürs mitmachen! Und ich hoffe, du hattest Spaß und machst weiterhin mit :) |
Vielen lieben Dank! ❤️ |
`SYVFH´RAQ2vX:FKG´gmZoXLvJgq4Gi§V´jf´epvMVJoE |
Description
This pull request fixes a bug in the edit-[challenge].vue component where the challengeData object was not properly initialized and validated. The issue caused methods like .trim() to be called on undefined values, leading to a TypeError. This change ensures that challengeData is properly checked before accessing its properties, thus preventing errors related to undefined attributes.
Type of change
Fixes Bootstrap-Academy/Bootstrap-Academy#149
My Bootstrap Academy username: eremiya01