Add fallback for property tags that don't fully parse #8257
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.
Fixes for a few issues on the p5 site.
DEGREES and degrees() conflicts
Documentation.js parses the foundation module's properties like this, without a
namefield and with an error in the parsedpropertytag:This is because it's documented as
@property if, without a type, which Documentation.js doesn't like. We used to have some code to handle that but I accidentally removed it when refactoring the TS type generation, so this ensures that the Foundation section gets generated again.p5.Vector.add not showing up in search
Search currently omits things with empty descriptions, and the p5.Vector.add method had no description because the static version of this method has no description and was overwriting the non-static one. I think the order the methods were encountered changed and recently caused the static ones to "win" here.
A better longer-term fix would be to: