logseq / logseq/logseq

Property name obtained from the plugin SDK is camel cased

Open
#5,815 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

:type/bug plugins props
Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

What happened?

A property named to-delete is converted into toDelete when it's read through the plugin SDK via block.properties.

image

I don't think this auto conversion is appropriate. In this case, the property must still be manipulated through the name to-delete and not toDelete, getting a toDelete back is useless and misleading.

Reproduce the Bug

See above description.

Expected Behavior

No response

Screenshots

No response

Desktop Platform Information

App, 0.7.5, plugin SDK, 0.0.6

Mobile Platform Information

No response

Additional Context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the conversion through the plugin SDK using a property named to-delete, then trace how block.properties exposes that property. Done means the SDK preserves the to-delete name so it can be read and manipulated without receiving toDelete.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
api, developer-experience
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.