In the transition from fixed pre-defined fields to customizable fields, some of the early logic handling template creation and migration needs to e revisited.
e.g.
type should be defined
fail gracefully if it's not?
look for references to nodeDefs.type -- gracefully handle if not defined? or inject into template?
server-database.m_ValidateTemplate expects these fields to be present (for both nodes and edges):
notes
info
citation
category
This is probably part of template/preferences refinement.
In the transition from fixed pre-defined fields to customizable fields, some of the early logic handling template creation and migration needs to e revisited.
e.g.
typeshould be definednodeDefs.type-- gracefully handle if not defined? or inject into template?server-database.m_ValidateTemplateexpects these fields to be present (for both nodes and edges):notesinfocitationcategoryThis is probably part of template/preferences refinement.