Could we please get support for spaces in the name of various nodes? I can use snake case but our stakeholders would prefer spaces. alternatively possibly auto replace the underscores with spaces... (configurable possibly?)
c
chris
11/29/2022, 6:45 PM
This might be better posed as a gh issue, so that we can get full input from the community. Anecdotally, I don't think that we would end up adding whitespace to asset/op names, we keep the character set pretty restrictive intentionally.
c
Casper Weiss Bang
11/29/2022, 7:17 PM
Make sense. Can you enlighten me on why? I assume its due to pickling and URL/URI reasons, but I am possibly more thinking of a optional "display name" field - distinguishing between an identifier and a common name. For instance to distinguish different groups. I.e "📥 ingress" and "📤 egress" for ELT and reverse ELT or similar.
c
chris
11/29/2022, 7:25 PM
Correct regarding why we probably won't allow spaces within identifiers for ops / assets. I think it's reasonable to want to have distinct display names however, might be worth raising a gh issue for that.