Replies: 1 comment 11 replies
-
Without having thought about it thoroughly - is hard-coding such properties directly in the coordinator zome code not an option? |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want the ability to configure settings for my DNAs without altering the code and without using DNA properties (to avoid breaking integrity hash). Think how
.env
files are often used in other frameworks, except that end-users could modify these properties themselves for their installed apps.My proposal is we add
coordinator_properties
to the DNA manifest (outside of the modifiers), and add a function indna_info()
to read them. Or alternatively add an additional (optional)settings.yaml
file to the packed dna.Interested in hearing other options / approaches. I see a foot guns where coordinator properties are read in integrity code, and where properties are overwritten due to not being scoped by zome.
Beta Was this translation helpful? Give feedback.
All reactions