12 - Schema Improvements

[ghost]

This place is meant as Discussion place for the Schema Improvements rfc.

Tracking Issue: #712
Rfc Document: https://wiki.dendron.so/notes/8bc80164-6436-4c77-8077-7842f53a4a23.html

Please create a Separate comment/ response for each part of the Rfc to make it easier to navigate the Opinions about the Separate parts of the RFC.

[xeor]

Is some of the ideas from #745 worth adding to the RFC?

[ghost]

Honestly, I like the idea of actions, but one question I immediately get is, will a Schema have only one action, or could it have more?

• If it can have more maybe the command could show all schemas with defined actions as well as letting you type on the selection of a schema it shows all actions of that schema.
  Secondly, how reusable should these Actions be?
• I mean your example could be used for every Journal schema out there, but to make it easier to improve on this we may want to declare that if the action is defined on a Schema that becomes the child of another schema that the Patter / Id gets added to the schema.

  version: 1
  schemas:
  - id: journal
    desc: Journal notes
    action:
      variables:
        - name: "name"
           type: "text"
           default: ""
           msg: "What should the note suffix be?"
      # Must match pattern
      name: "journal.%Y.%M.%D $name$"
  -id: projects
    namespace: true
    children:
      - journal

  That this would result in "projects.foo.journal.2020.01.01.$Name"

Thirdly, Could an action be extended, by providing additional Variables and changing the result?

• Either adding an additional prefix or sufix

In Relation to the Rfc I would Probably think about adding actions as a Type.

[xeor]

Maybe actions can be defined up the tree? So if you want an action that you can use globally, define it in root.schema..
You could then define actions as actionName, instead of action. actionName and action are mutually exclusive.

The variables defined in an action could later be of type script to populate variables based on external input.
Other types can be staticList, regexList?, ...

They should run in order and not be async since they collect user input from popup-boxes, and or scripts (later).
Variables collected should also be available when collecting asking for another variable. This way, we can create a very dynamic experience when a schema is run..

[ghost]

In relation to the Json-schema part of the Rfc
I already started working on something here https://github.com/flammehawk/dendron-schemas