Naming and best practice

Setting the state correctly is important due to our online help, since the online help link is based on the state. When a state changes, it will result in a new online help link which may cause customers to meet an empty page if this has not been handled in the online help. Therefore, avoid creating temporary or hidden states as much as possible. Talk to Lina if changing states or adding new ones.

When creating a new state, name it using "spinal-case".

When working to replace an existing state, name the new state "state-name-new" until its ready. When it is, replace it with "state-name".

Note: "config" cannot be used as a child state name.

function stateConfig($stateProvider) {
  $stateProvider.state('example',
  {
    url: '/example',
    templateUrl: 'app/example/example.html',
    controller: 'ExampleController'
  })
  .state('example.child',
  {
    url: '/child',
    templateUrl: 'app/example/example-child.html',
    controller: 'ExampleChildController'
  })
  .state('example.another-view',
  {
    url: '/another-view',
    templateUrl: 'app/example/another-view.html',
    controller: 'ExampleSecondViewController'
  })
}
      

Add translation keys to the resource file and provide the string and a description. If you need to change the string on a previously added key, please choose one of the following options:
Remove the key completely (in all translation files as well) and add a new key OR Change the string for the original key, and delete all previous translation of that key