Repository navigation
Fix: Properly handle optional author and description properties - #315
Merged
Merged
Conversation
Member
|
Would it make more sense to use these functions? streaming-website/model/Conference.php Line 22 in cc6bb04 |
CommanderRedYT
approved these changes
Sep 24, 2026
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
2 participants
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.
The
organizeranddescriptionproperties are not mandatory (or weren't until somebody spontaneously changed the schema) in theconfig-schema.jsonand according to their descriptions "Ist das Feld leer, wird kein solcher -Tag generiert."So the proper fix is to handle the absence of these properties properly.