Replies: 1 comment
-
I've moved this over to "Ideas" since this is a feature request rather than a bug. I think frontmatter handling could definitely be more refined, and I'd welcome a pull request adding better frontmatter handling! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem Description
When using the PATCH operation with
append
to add a single item to an existing frontmatter array, the API returns a 500 error:"Cannot merge objects of different types or unsupported types: object and string"
.Expected Behavior
The
append
operation should intelligently handle different frontmatter field types:Current Behavior
The API fails when trying to append a string value to an existing array field.
Reproduction Steps
Error Response
Proposed Solution
The API should detect the target field type and handle append operations accordingly:
For Array Fields:
For String Fields:
Use Cases
This enhancement would enable:
append
individual tags without needing to read existing tags firstWorkaround
Currently, clients must:
This creates unnecessary complexity and multiple API calls for a simple append operation.
Additional Context
This issue affects any automation or integration that wants to incrementally build frontmatter arrays, which is a common use case for note management workflows.
Thanks for building this awesome API! It's been incredible for implementing cool automation and integration projects. Keep up the great work! 🎉
Beta Was this translation helpful? Give feedback.
All reactions