RavenDB adapter

I have built my own adapter for RavenDB. Raven is a document database and when I use the organization plugin I get JSON as a string in the metadata. Is it possible to make better auth not to serialize the metadata field as a string? Is this metadata needed for the organization plugin to work? This is how the document look like in RavenDB.
{
"name": "Marcus plats",
"slug": "marcus-plats",
"logo": "🏢",
"createdAt": "2025-09-04T17:24:54.7130000",
"metadata": "{\"createdFromLocal\":true,\"domain\":\"marcus-plats\",\"createdAt\":\"2025-09-04T15:24:54.667Z\",\"updatedAt\":\"2025-09-04T15:24:54.667Z\"}",
"@metadata": {
"@collection": "Organizations",
"@nested-object-types": {
"createdAt": "date"
},
"Raven-Node-Type": null
}
}
{
"name": "Marcus plats",
"slug": "marcus-plats",
"logo": "🏢",
"createdAt": "2025-09-04T17:24:54.7130000",
"metadata": "{\"createdFromLocal\":true,\"domain\":\"marcus-plats\",\"createdAt\":\"2025-09-04T15:24:54.667Z\",\"updatedAt\":\"2025-09-04T15:24:54.667Z\"}",
"@metadata": {
"@collection": "Organizations",
"@nested-object-types": {
"createdAt": "date"
},
"Raven-Node-Type": null
}
}
1 Reply
Ping
Ping2mo ago
Yeah this is normal, we don't fully support JSON yet so we convert to strings

Did you find this page helpful?