We recently switched FC from .PascalCase to .traditional-case selectors (#346).
There is no issue with this change itself, but it's made upgrading some older projects from older version of FC just about impossible -- at least without having to involve back-end developers with changing their CSS class names on their end too.
The solution we've agreed on as a team is to create a setting somewhere in FC that reverts our scaffolding back to PascalCase. There is no need to involve the base elements in this change, because it's intended for folks who are using old versions of FC, so they wouldn't be touching the base elements as part of their upgrade plan (they'd just be bringing over the new build system and dependencies).
Approach
Add a setting in fc-config.js called pascalStyles (or something similar, I am open to suggestions) that is defaulted to false.
Build logic into the scaffolding system that uses the old PascalCase naming convention if that setting is flipped to true, but otherwise operate normally.
We recently switched FC from
.PascalCaseto.traditional-caseselectors (#346).There is no issue with this change itself, but it's made upgrading some older projects from older version of FC just about impossible -- at least without having to involve back-end developers with changing their CSS class names on their end too.
The solution we've agreed on as a team is to create a setting somewhere in FC that reverts our scaffolding back to PascalCase. There is no need to involve the base elements in this change, because it's intended for folks who are using old versions of FC, so they wouldn't be touching the base elements as part of their upgrade plan (they'd just be bringing over the new build system and dependencies).
Approach
Add a setting in
fc-config.jscalledpascalStyles(or something similar, I am open to suggestions) that is defaulted tofalse.Build logic into the scaffolding system that uses the old PascalCase naming convention if that setting is flipped to
true, but otherwise operate normally.