microlinkhq / metascraper / 23362113695
94%

DEFAULT BRANCH: master
Ran
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
23362113695

push

github

web-flow 
feat: defuddle (#829)

* feat: defuddle

* test: update snapshot

* perf: add benchmark

* chore: capture defuddle errors

* test: validation

* perf: one loop

* test: update snapshot

* test: update snapshot

* test: update snapshot

* test: update snapshot

* test: update snapshot

* test: update snapshot

* fix: skip JSON-LD structural keys (@-prefixed) in recursive schema search

The non-exact recursive search in searchSchemaResults iterated over all
object keys including @context, @type, etc. When @context is an object
(e.g. containing property namespace definitions), property names inside
it could match and return schema definition URLs instead of actual
content values.

Made-with: Cursor

* fix: treat null JSON-LD properties as missing in $jsonld fallback

`get()` returns `null` for explicitly null properties, but the loop
guard used strict `!== undefined`, preventing the recursive
searchSchemaResults fallback from running. Similarly,
searchSchemaResults returned early with an empty result when
hasOwnProperty matched a null value, blocking the non-exact
recursive traversal.

Both checks now correctly fall through for null values, allowing
nested properties to be discovered.

Made-with: Cursor

* fix: remove unconditional object-to-name resolution in $jsonld

The object-to-name block converted any object with a string `.name`
into that name, regardless of what the caller expected. This broke
callers like `$jsonld('image')` and `$jsonld('publisher')` that need
the full object for downstream validators (toImage, toLogoUrl).
The recursive fallback via searchSchemaResults already handles
object-to-name resolution where appropriate.

Made-with: Cursor

* refactor: extract common helpers

* fix: join multiple values from exact JSON-LD schema search in $jsonld fallback

When searchSchemaResults traverses an explicit property path (e.g.,
author.name) through an array of objects, multiple resolved values are
now joined with " and " instead of discarding... (continued)
Source Files on build 23362113695
Detailed source file information is not available for this build.