Explain the problem as you see it
Fields' settings like initialization or hiding rules are global. However, we can often use one field in under multiple supertags and in each case our initialization/hiding rules would be different.
Why is this a problem for you?
Creating separate fields for all supertags looks ugly and creates mess.
Suggest a solution
Fields settings based on a supertag, not global
2 Comments
I have lot of duplicate fields rn because the context of different tag need different config.
It's a shame I have to give up such powerful fields customizability due to context conflicting between tags.
agreed! especially where those are linking fields between data clusters (e.g. client <-> project) where the client CRM data is essentially not deeply integrated in the task / todo structure of project management
1st priority: setting the default values based on ancestor nodes or sibling nodes
2nd priority: required or not required
3rd priority: display or hide when empty
side note: would this be hard to do if it is in an extended supertag? e.g. fields in todos inherit from the parent node but a project which could be an extension of the todo base tag inherit from the associated client node
nice to have: move it up or down in hierarchy when it is from an extended supertag