fixes/454-undefined-cookingTime-is-now-correct #468
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the issue [#454 – cookingTime is Undefined].
The cookingTime property was not being defined/initialized properly, which resulted in runtime errors when rendering recipes.
Added proper handling and default value assignment for cookingTime.
Ensured that the property is consistently available when new recipes are created or fetched from the API.
Changes Made
Added fallback/default value for cookingTime.
Updated recipe creation logic to include cookingTime.
Minor cleanup for better code consistency.
Testing
Verified that new recipes now include a valid cookingTime.
Confirmed that fetching and rendering recipes no longer throws the undefined error.
Fixes #454 ✅