-
Notifications
You must be signed in to change notification settings - Fork 33
External CSS file for Form styles #1001
Copy link
Copy link
Open
Labels
area/artifact-managerRelates to the `artifact-manager` maven moduleRelates to the `artifact-manager` maven moduleeffort/mediumkind/featureNew Feature to the projectNew Feature to the projectlang/javaRelated to Java CodeRelated to Java Codetriage/neededNeeds to be discussed by project maintainersNeeds to be discussed by project maintainersversion/minorIntroduces a non-breaking feature or changeIntroduces a non-breaking feature or change
Description
Metadata
Metadata
Assignees
Labels
area/artifact-managerRelates to the `artifact-manager` maven moduleRelates to the `artifact-manager` maven moduleeffort/mediumkind/featureNew Feature to the projectNew Feature to the projectlang/javaRelated to Java CodeRelated to Java Codetriage/neededNeeds to be discussed by project maintainersNeeds to be discussed by project maintainersversion/minorIntroduces a non-breaking feature or changeIntroduces a non-breaking feature or change
Description
We frequently need to apply custom CSS to our forms. At the moment, this CSS is stored as an escaped string within the styles key of the form’s
.jsonfile. To make future changes easier, we also keep a separate .css file alongside the JSON. However, this approach requires manual effort to keep both files in sync, especially when pulling changes.It would be helpful if the contents of the
stylesfield were written out to an external.cssfile on pull and read from that file when pushing changes. Ideally, this file would follow the same naming convention as the form’s.jsonfile (for example,*_FormData.json). This would greatly improve the authoring and maintenance experience for custom styles.Alternatives
Continue working with escaped CSS strings in JSON, or build custom local tooling to extract and generate a .css file from the styles key.