@oblique/oblique
Advanced tools
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 mas
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.
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.
ng add @oblique/oblique. This interactive command will:
tslint with eslint and prettierng updateng update @oblique/obliquenpm updatenpm outdatednpm i -g @angular/cligit clone https://github.com/oblique-bit/oblique.git.npm cinpm run themesnpm startnpm testWe 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:
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:
The scope is optional and should be the name of the Oblique feature affected:
The subject is mandatory and contains a succinct description of the change:
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`
FAQs
An Angular front-end framework tailored for your swiss branded business web application.
The npm package @oblique/oblique receives a total of 554 weekly downloads. As such, @oblique/oblique popularity was classified as not popular.
We found that @oblique/oblique demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.