An Angular front-end framework Tailored for your swiss branded business web application, Oblique provides a standardized corporate design look and feel as well as a collection of ready-to-use Angular components. Oblique, through its fully customizable master layout, takes care of the application's structure, letting you focus on the content.
For questions and support please contact us by email.
Read the developer docs: https://oblique.bit.admin.ch/
Oblique uses npm, AngularCLI and Sass to fetch dependencies, compile & build assets, compose HTML and serve & watch web content.
- Update your project to Angular 9: https://update.angular.io/#8.0:9.0
- Add Oblique to your project:
ng add @oblique/oblique. This interactive command will:- add oblique and its dependencies
- refactor your application to integrate Oblique
- optionally replace jasmine with jest
- optionally configure Sonar
- optionally configure Jenkins & Cloud Foundry
- optionally replace
tslintwitheslintandprettier - optionally add a git hook to auto format files before push
- optionally add IE11 support
- Bump dependencies through Angular cli first:
ng update - Then update oblique:
ng update @oblique/oblique - Finally update the dependencies without build-in schematics:
npm update - New major versions can be discovered through
npm outdated
- GIT
- nodejs & npm
- AngularCli installed globally:
npm i -g @angular/cli
- Clone the repo:
git clone https://github.com/oblique-bit/oblique.git. - Install project dependencies:
npm ci - Generate the theme files:
npm run themes - start the showcase:
npm start - start the tests:
npm test
We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. The git commit messages will also be used to generate Oblique's change log.
For better readability, please follow the following rules:
- 1 commit per change, fixes have to be squashed together.
- A change includes its tests, mocks, documentation and schematics.
- 1 commit concerns 1 scope (see below), if a commit spans multiple scopes, split it into several commits. Exception: changes that spans most of the library can be grouped together. In that case, there is no scope
- no line of the commit message can be longer than 100 characters.
- changes to the showcase should NEVER come with another type (see below) as showcase. All showcase changes of an issue should be squashed together
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject>
<body>
<footer>
The header is mandatory and lowercase only. The scope of the header is optional. There no space between type and scope.
The type is mandatory and must be one of the following:
- feat: Changes that creates, improves or removes a feature
- fix: Changes that fixes a bug
- refactor: Changes to a feature that neither adds, removes nor fixes a behavior
- test: Changes that affect tests and their configuration only
- docs: Changes that affect the documentation only
- showcase: Changes that affect the showcase only
- format: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- chore: Anything that do not fit in any previous types (e.g. release, dependencies update, ...)
The scope is optional and should be the name of the Oblique feature affected:
- alert
- button
- collapse
- column-layout
- datepicker
- document-meta
- dropdown
- error-messages
- external-link
- form-control-state
- global-events
- http-interceptor
- input-clear
- icon
- language
- master-layout
- multi-translate-loader
- multiselect
- nav-tree
- nested-form
- notification
- number-format
- off-canvas
- popover
- pop-up
- schema-validation
- scrolling
- search-box
- selectable
- spinner
- sticky
- translate-params
- unknown-route
- unsaved-changes
- bootstrap (for bootstrap components or styles)
- material (for material design components or styles)
- schematics (for the schematics not directly linked to a feature)
- styles (for the global CSS)
- theme (for the theme service)
- toolchain (for the configuration, build, releases...)
- translation (for the translations not directly linked to a feature)
- utilities (for utilities.ts)
The subject is mandatory and contains a succinct description of the change:
- use the imperative, present tense: "change" not "changed" nor "changes"
- don't capitalize the first letter
- no dot (.) at the end
The body is optional. Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
The footer is optional and should contain a reference to a JIRA issue if any, e.g.: OUI-715.
It should also contain any information about Breaking Changes.
Breaking Changes have to start with the words BREAKING CHANGE: followed by a newline. The rest of the commit message is then used for this. Multiple breaking changes can be displayed with bullet points
OUI-715
BREAKING CHANGE:
* function `funcA` has been removed in favor of `funcB`
* property `prop` has been removed with no replacement
* file `fileName` has been renamed into `myFile`