open-index/open-npm huggingface dataset:
npm package: @informatiqal/automatiqal-schema
Description: Automatiqal runbooks JSON and pseudo UI schemas
Author: Informatiqal @informatiqal
Latest version: 0.23.0

# Automatiqal CLI (JSON schema)

## UNDER DEVELOPMENT

This repository contains JSON schema that can be used when writing [Automatiqal CLI](https://github.com/Informatiqal/automatiqal-cli) runbooks.

## Installation

```shell
npm install --save @informatiqal/automatiqal-schema
```

### Exports

The package exports three constants:

- `automatiqalWindowsSchema` - valid [JSON schema (Draft-07)](https://json-schema.org/) for interacting with QSEoW
- `automatiqalSaaSSchema` - valid [JSON schema (Draft-07)](https://json-schema.org/) for interacting with Qlik Cloud/SaaS
- `automatiqalUISchema` - pseudo schema that can be used in UI projects. **This is not a valid JSON schema** and its under development so please do not use

## VSCode

First make sure you have [YAML](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml) extension installed. This extension will give YAML language support in VSCode

After that there are two ways to use the schema: inline (local) and as user setting (global).

### **Inline**

Inline method is applied to each individual yaml runbook file.

Add the following line to the top of the runbook yaml file:

- for QSEoW
    `# yaml-language-server: $schema=https://github.com/Informatiqal/automatiqal-cli-schema/blob/main/schemas/runbook.json?raw=true`

- for SaaS
    `# yaml-language-server: $schema=https://github.com/Informatiqal/automatiqal-cli-schema/blob/main/schemas/runbook_saas.json?raw=true`

Or if the schema is downloaded locally:

`# yaml-language-server: $schema=c:\path\to\runbook.json`

### **User settings**

- `Ctrl + Shift + p`
- search for `Preferences: Open User Settings`
- search for `schema`
- click on `JSON`
- click on `Edit in settings.json` (`JSON: Schemas` section)
- add new entry

  ```json
  {
    "fileMatch": ["/*.something.yaml"],
    "url": "https://github.com/Informatiqal/automatiqal-cli-schema/blob/main/schemas/runbook.json?raw=true"
  }
  ```

  `*.something.yaml` - the schema in this case will be applied to all files that have `something.yaml` in their name. Replace `something` with whatever you want.
npm package: @informatiqal/filter-parser
Description: Library to parse Qlik filter into JS format
Author: Informatiqal @informatiqal
Latest version: 0.1.0

# Automatiqal filter parser

## Description

Small (**and very specific**) package to parse `Automatiqal` conditions and covert them to JS.

These condition are quite similar to `Qlik Repository` filtering format.

## Usage

```js
import { parseFilter } from "@informatiqal/filter-parser";

const parsed = parseFilter("(('something' so 'thing' and 1 eq 1) or 3 gt 4)")

```

Once executed the value of `parsed` (string) will be:

```js
(('something'.includes('thing') && 1 == 1) || 3 > 4)
```

The returned string can then be evaluated to get the result of it. In the example above the result will be `true`.

## Base path

**UNDER DEVELOPMENT**
**Please do not use at the moment!**

The main function accepts additional parameter - base path. Extending the example above:

```js
import { parseFilter } from "@informatiqal/filter-parser";

const parsed = parseFilter("(('something' so 'thing' and 1 eq 1) or 3 gt 4)", "myObj")

```

Will return:

```js
((myObj.something.includes('thing') && myObj.1 == 1) || myObj.3 > 4)
```

## Available operators

### Math

- eq - equal `==`
- ne - not equal  `!=`
- gt - grater than `>`
- ge - greater than or equal `>=`
- lt - less than `<`
- le - less than or equal `<=`

### String

- sw - starts with
- ew - ends with
- so - substring of
npm package: @informatiqal/publiqate-html
Description: Publiqate plugin to generate HTML files
Author: Informatiqal @informatiqal
Latest version: 1.0.0

# Publiqate HTML

Generate HTML file plugin for `Publiqate`

## Build and Installation

Clone this repository. Navigate to the `plugins -> html` folder and run:

```bash
npm run build
```

Once the build process is complete the compiled code will be available in `plugins -> html -> dist` folder.

Copy the content of the `dist` folder somewhere on the server, where `Publiqate` is running and specify the location from where `Publiqate` will load the plugin.

Once the config is set either restart the `Publiqate` service or visit the admin UI and press "Refresh config".

Example config:

```yaml
...
plugins:
  - c:\path\to\html\plugin\dist\index.js
...
notifications:
  - type: Stream
    ...
    callbacks:
      - type: html
        details:
          template: c:\path\to\template.handlebars # see Templates section for details
          path: c:\path\to\where\to\store\index.html
          type: handlebars # or ejs, pug, mustache
...
```

## Options

- `template` - full path to the template to use (see `Templates` section for details)
- `path`- full path to where to store the compiled plugin. The path must include the file name as well
- `type` - optional. defaults to `handlebars`. Which template engine to use to render the template (see the section below)

## Templates

The plugin support 4 template engines:

- [ejs](https://ejs.co/)
- [handlebars](https://handlebarsjs.com/guide/) - **default**
- [pug](https://pugjs.org/api/getting-started.html)
- [mustache](https://github.com/janl/mustache.js)

For each template engine error log entry will be generated if the template fails to compile/render.

Examples how to render list of names for all entities in the notification for each template engine:

### [EJS](https://ejs.co/)

```ejs
<ul><% entities.forEach((entity,index) => {%>
  <li><%= entity.details.name %></li><% }) %>
</ul>
```

### [Handlebars](https://handlebarsjs.com/guide/)

```handlebars
<ul>
  {{#each entities}}
    <li>{{this.details.name}}</li>
  {{/each}}
</ul>
```

### [Pug](https://pugjs.org/api/getting-started.html)

```pug
ul
  each n in entities
    li= n.details.name
```

### [Mustache](https://github.com/janl/mustache.js)

```mustache
<ul>
  {{#entities}}
    <li>{{details.name}}</li>
  {{/entities}}
</ul>
```
npm package: @informatix8/access-search
Description: Vue components for Search BIOS
Latest version: 2.1.0

# Access Search

Vue components for Search BIOS

## Usage

### Install

```shell
npm install @informatix8/access-search --save-dev
```

### CDN

```html
<script src="https://unpkg.com/@informatix8/access-search/dist/access-search-vue.umd.min.js"></script>
```

## Development

```shell
npm run dev
```

## Build

```shell
npm run build
```

## Release

```shell
npm run build
git tag -a vX.Y.Z
git push origin master
git push origin --tags
npm publish --access=public .
```
npm package: @informe/web-ui
Description: This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.1.1.
Latest version: 0.0.19-alpha.0

# Ui

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.1.1.

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.

## Code scaffolding

Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.

## Build

Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.

## Running unit tests

Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).