Allow property names to start with number or special characters (as obsidian does natively)

[Void4m0n]

Please fill out these Check-boxes

• I checked for existing similar feature requests
• I have read the docs and checked that the feature I am requesting is not already implemented
• My feature request consists of only one feature

Is your Feature Request related to a Problem or Annoyance?

I am developing an application to record training sessions, and to record the training data in the properties of the file I use an input field with the following format: INPUT[number(class(moible_input)):${exercise_name}_reps_set_${c}. The problem is that input fields do not allow the property name to start with a number or some special characters (although obsidian natively supports this). So in my case when exporting a json with more than 800 exercises to .md notes causes that exercises starting with a number will return the following error:

If the property starts with text characters there is no problem. INPUT[number(class(moible_input)):exercise_3_4_sit_up_reps_set_1]

Describe the Feature you'd like

It would make sense to me that metabind would support the same characters that obsidian supports by default when parsing the property name.

Alternatives

Parse the property name between : ] allowing the same characters as obsidian allows at the beginning of the property:

• Numbers
• Special characters like / ; ( ) < >

Additional Context

Your plugin is amazing! ty for the work

[mProjectsCode]

have you tried INPUT[number(class(moible_input)):["${exercise_name}_reps_set_${c}"]]?

[mProjectsCode]

The plugin closely follows JS syntax for accessing properties

[Void4m0n]

Works perfectly, however, checking the documentation and the example vault I have not found any reference to the use of [""] in the property field, maybe it would be interesting to document it to avoid future questions. Thanks for the solution!

[mProjectsCode]

see https://www.moritzjung.dev/obsidian-meta-bind-plugin-docs/guides/bindtargets/#3-the-property

[Graywaren]

How do you do this in buttons for updating metadata? [""] works as explained in that documentation for inputs, but it doesn't work for metadata bind targets in buttons. quotes without the bracket don't work either. I've not been able to find a reference to it anywhere, which is surprising as I thought it would have come up for spaces at least. I'd really rather not make templater templates to have the buttons run to do this instead

[mProjectsCode]

It works the same for buttons. See below for an example.

label: This is a button
style: default
actions:
  - type: updateMetadata
    bindTarget: '["foo bar"]'
    evaluate: false
    value: baz

[Graywaren]

Thank you!!!! It was that outer set of '' I was missing. I tried '' without the brackets, "" without, [""] etc. but missed the combination of all three.