Home - luftsport/nlf-client GitHub Wiki

Welcome to the nlf-client wiki!

Structure of nlf-client:

• REST Api defined in api/
• Applications are prefixed "nlf-*"
• Services in services/
  • Authentication in services/auth

Structure of nlf-client

The structure is as in a collection of applications with shared resources.

• All logical application containers are all prefixed nlf- and placed in root
• The main files of the respective applications are also prefixed nlf- in the applictions respective root
• Further logical subapplications are not prefixed
• Shared resources are not prefixed

Example directory structure:

app/
    nlf-user/
        nlf-user.component.ts
        nlf-user.template.ts
        user-settings/
            user-settings.component.ts
            user-settings.template.ts
    resolve/
        resolve-user/
            resolve-user.component.ts

nlf-user/ is a logical container for the user application with the component having selector nlf-user and classname NlfUserComponent.

nlf-user/user-settings/ is the logical container for the users' settings with the component having the selector nlf-user-settings and classname NlfUserSettingsComponent

resolve/ is the logical container for all resolvers. All resolver selectors are prefixed nlf-resolve- and classnames NlfResolve

Selectors and classnames

• All selectors shall be prefixed nlf- regardsless of the file being prefixed or not
• Selectors naturally exposing the organization structure should be prefixed accordingly eg nlf-fallskjerm-, nlf-motor-
• All classnames shall be prefixed Nlf following the structure of the selectors from - to camelcase