Rekit forces consistent naming rules by auto converting the input. Either command line tools or Rekit portal follow below naming rules to create features, components and actions. If you create them manually should also follow the rules.
feature: Folder name: kebab case. For example:
rekit add feature myFeaturewill create a folder named
redux store: camel case. When adding a feature, Rekit will combine the feature reducer to the root reduer with the camel case as the branch name.
url path: kebab case. It's converted from the
-u MyPageargument as it's always mapped to a page. For this command, it defines url path as 'my-page' in the route config.
component: File name and style file name: pascal case. For example:
rekit add component feature/my-componentwill create files
action: Function name: camel case. For example:
rekit add action feature/my-actionwill create a function named
action type: Constant name and value: upper snake case. Action types are created when an action is created. For example:
rekit add action home/my-actionwill create a action type
As you see, whatever names provided as arguments will be converted. So that all variables namings of a Rekit application are always consistent and easy to understand.