I'm working on registering project/etc metadata with our own resolver. The webapp requests and receives this metadata but crashes the project page: https://dev.app.regen.network/project/MBS01-001
Clicking through the console error trace I found:
function W(r) {
return r.split(":")[1].replace(/([A-Z])/g, " $1")
}
Searching codebase for /([A-Z])/g brings me to this:
Notice that our data resolver returns a compacted serialization with a hard-coded context and includes @graph. It seems like regen web isn't compatible with this. At minimum I wouldn't expect this to crash the page.
I'm working on registering project/etc metadata with our own resolver. The webapp requests and receives this metadata but crashes the project page: https://dev.app.regen.network/project/MBS01-001
Clicking through the console error trace I found:
Searching codebase for
/([A-Z])/g
brings me to this:https://github.com/regen-network/regen-web/blob/1f306059c5f5a0b3229ddf1f9464a0a938f19e53/web-marketplace/src/lib/rdf/rdf.unknown-fields.ts#L94-L96
Below is the metadata I'm currently testing with (note the live version might change as I'm actively working on the resolver) - it seems like the regen webapp might not be compatible with all jsonld serializations? This metadata is a copy of the metadata C06-001 on mainnet with some text values changed: https://api.regen.network/data/v1/metadata-graph/regen:13toVhTxrr61w3iaLGGQL5AzmX9ss9DfQcuUATgT4L2dBb947DrAm2b.rdf
Notice that our data resolver returns a compacted serialization with a hard-coded context and includes
@graph
. It seems like regen web isn't compatible with this. At minimum I wouldn't expect this to crash the page.