![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
@ssv/ngx.ux
Advanced tools
Readme
UX essentials for building apps, utilities which enables you writing richer apps easier.
Quick links
Change logs | Project Repository
Get library via npm
npm install @ssv/ngx.ux
Choose the version corresponding to your Angular version:
Angular | library |
---|---|
15 | 2.x+ |
4 to 9 | 1.x+ |
import { SsvUxModule } from "@ssv/ngx.ux";
@NgModule({
imports: [
SsvUxModule
]
}
export class AppModule {
}
Provides utilities to handle responsiveness easier based on the viewport (view size)
Operand | Description |
---|---|
= | Equals |
<> | Not equals |
< | Less than |
<= | Less than or equal |
> | Greater than |
>= | Greater Than or equal |
These are the defaults, but they are configurable.
Size Type | Size Range |
---|---|
xsmall | <=450 |
small | 451-767 |
medium | 768-992 |
large | 993-1280 |
fhd | 1281-1920 |
qhd | 1921-2560 |
uhd4k | 2561-3840 |
uhd8k | >=3841 |
Structural directive which loads components based on a viewport sizing condition e.g. show ONLY if viewport is greater than xlarge.
<!-- simple -->
<div *ssvViewportMatcher="'large'">
show only when large
</div>
<!-- expression based - tuple (shorthand) *recommended usage* -->
<div *ssvViewportMatcher="['>=', 'xlarge']"> (see all operands and sizes)
show when >= xlarge
</div>
<!-- expression based - object -->
<div *ssvViewportMatcher="{size: 'xlarge', operation: '<='}"> (see all operands and sizes)
show when >= xlarge
</div>
<!-- includes -->
<div *ssvViewportMatcher="['large', 'xlarge']">
show only when large, xlarge
</div>
<!-- excludes -->
<div *ssvViewportMatcher="''; exclude ['xsmall', 'small']">
hide only when xsmall, small
</div>
<!-- match/else -->
<div *ssvViewportMatcher="['>=', 'xlarge']; else otherwise">
show when >= xlarge
</div>
<ng-template #otherwise>
show when expression is falsy (< xlarge)
</ng-template>
<!-- non structure syntax -->
<ng-template ssvViewportMatcher [ssvViewportMatcherExclude]="'xsmall'">
(exclude xsmall)
</ng-template>
Structural directive which provides the condition var whether it matches or not (params are similar to ssvViewportMatcher
).
<!-- simple -->
<div *ssvViewportMatcherVar="let isLarge when 'large'">
isLarge={{isLarge}}
</div>
<!-- expression based - tuple (shorthand) *recommended usage* -->
<div *ssvViewportMatcherVar="let isMediumDown when ['<=', 'medium']">
isMediumDown={{isMediumDown}}
</div>
<!-- includes/or -->
<div *ssvViewportMatcherVar="let isLargeOrSmall when ['small', 'large']">
isLargeOrSmall={{isLargeOrSmall}}
</div>
// get size type
this.viewport.sizeType$.pipe(
tap(x => console.log("Viewport - sizeType changed", x)), // { type: 4, name: "xlarge", widthThreshold: 1500 }
).subscribe();
Since in SSR there is no way to know the client viewport size, we should at least determine device type and handle provide
3 different sizes based on device type e.g. mobile
, tablet
or desktop
so the initial rendering will be closer based on device type.
The basic implementation allows to provide a device type mobile
, tablet
or desktop
and there are static sizes for those.
import { UX_VIEWPORT_SSR_DEVICE } from "@ssv/ngx.ux";
const deviceType = deviceTypeFromServer;
{ provide: UX_VIEWPORT_SSR_DEVICE, useValue: deviceType },
The default implementation can also be replaced by implementing a small class as following:
export class SuperViewportServerSizeService {
get(): ViewportSize {
// do your magic..
return size;
}
}
import { ViewportServerSizeService } from "@ssv/ngx.ux";
@NgModule( {
providers: [
{ provide: ViewportServerSizeService, useClass: SuperViewportServerSizeService }
]
}) export class AppModule {
}
You can configure the existing resize polling speed and as well as provide your custom breakpoints.
import { SsvUxModule, generateViewportSizeType } from "@ssv/ngx.ux";
const breakpoints = { // custom breakpoints - key/width
smallest: 500,
small: 700,
medium: 1000,
large: 1400,
extralarge: 1600,
xxlarge: 1800,
fhd: 1920,
uhd: 3840
};
imports: [
SsvUxModule.forRoot({
viewport: {
resizePollingSpeed: 66, // optional - defaults to 33
breakpoints // provide the custom breakpoints
}
}),
],
import { SsvUxModule, UX_VIEWPORT_DEFAULT_BREAKPOINTS } from "@ssv/ngx.ux";
imports: [
SsvUxModule.forRoot({
viewport: {
breakpoints: {
...UX_VIEWPORT_DEFAULT_BREAKPOINTS, // use breakpoints provided with library
xxlarge1: 2000, // override xxlarge1
uhd: 3840 // add new breakpoint
}
}
}),
],
Install/setup the following:
npm install -g git gulp devtool
The following process need to be executed in order to get started.
npm install
npm run build
npm test
Handles compiling of changes.
npm start
Spawns test runner and keep watching for changes.
npm run tdd
Check out the release workflow guide in order to guide you creating a release and publishing it.
FAQs
UX essentials for building apps, utilities which enables you writing richer apps easier.
We found that @ssv/ngx.ux demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.