Some section titles include parentheses and others do not, so please standardize this and, if possible, omit the parentheses unless they serve a specific purpose — which I am not aware of.
Why strip parentheses on the frontend instead of fixing the backend
The category strings like (Info) and (Schema Item) come from C# [Category("(Info)")] attributes on properties in Origam.Schema/AbstractSchemaItem.cs and several entity-model schema items. The parentheses are a legacy WinForms PropertyGrid convention: since categories are sorted alphabetically and ( has a lower ASCII value than any letter, wrapping a category name in parentheses pushes it to the top of the list (so (Info) and (Schema Item) appear before Entity, Mapping, etc.).
The HTML Architect also sorts categories alphabetically, so the same ordering effect is preserved even without showing the parentheses — (Info) still sorts before Entity regardless of whether we render the parens.
Removing the parentheses from the C# [Category(...)] attributes would affect the legacy WinForms Architect too, which still relies on that exact ASCII-sort trick for ordering. That is a wider blast radius and would require revisiting category ordering across the entire old client.
Doing the cleanup at the render site in PropertyEditor.tsx is:
-
scoped strictly to the HTML Architect UI,
-
a one-line, reversible change,
-
preserves the sort order (we strip parens only for display, not for the sort key),
-
and avoids touching shared backend metadata used by another client.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.