open-index/open-npm huggingface dataset:
npm package: @gsp-sys/audit-eventhelp
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.5

# Audithelp

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

## Code scaffolding

Run `ng generate component component-name --project audithelp` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project audithelp`.
> Note: Don't forget to add `--project audithelp` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build audithelp` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build audithelp`, go to the dist folder `cd dist/audithelp` and run `npm publish`.

## Running unit tests

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

## 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).
npm package: @gsp-sys/framework-workbench
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 2.0.8

# FrameworkWorkbench

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project framework-workbench` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project framework-workbench`.
> Note: Don't forget to add `--project framework-workbench` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build framework-workbench` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build framework-workbench`, go to the dist folder `cd dist/framework-workbench` and run `npm publish`.

## Running unit tests

Run `ng test framework-workbench` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-sys/framework-workbentch
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.1

# FrameworkWorkbentch

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

## Code scaffolding

Run `ng generate component component-name --project framework-workbentch` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project framework-workbentch`.
> Note: Don't forget to add `--project framework-workbentch` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build framework-workbentch` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build framework-workbentch`, go to the dist folder `cd dist/framework-workbentch` and run `npm publish`.

## Running unit tests

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

## 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).
npm package: @gsp-sys/rtf-apphelp
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 1.0.11

# Rtffunchelp

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project rtffunchelp` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project rtffunchelp`.
> Note: Don't forget to add `--project rtffunchelp` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build rtffunchelp` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build rtffunchelp`, go to the dist folder `cd dist/rtffunchelp` and run `npm publish`.

## Running unit tests

Run `ng test rtffunchelp` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-sys/rtf-common
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 2.0.11

# GspRtf

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project gsp-rtf` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project gsp-rtf`.
> Note: Don't forget to add `--project gsp-rtf` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build gsp-rtf` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build gsp-rtf`, go to the dist folder `cd dist/gsp-rtf` and run `npm publish`.

## Running unit tests

Run `ng test gsp-rtf` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-sys/rtf-production-help
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 1.0.11

# Rtffunchelp

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project rtffunchelp` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project rtffunchelp`.
> Note: Don't forget to add `--project rtffunchelp` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build rtffunchelp` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build rtffunchelp`, go to the dist folder `cd dist/rtffunchelp` and run `npm publish`.

## Running unit tests

Run `ng test rtffunchelp` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-sys/rtf-ui
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 1.1.12

# Rtffunchelp

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project rtffunchelp` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project rtffunchelp`.
> Note: Don't forget to add `--project rtffunchelp` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build rtffunchelp` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build rtffunchelp`, go to the dist folder `cd dist/rtffunchelp` and run `npm publish`.

## Running unit tests

Run `ng test rtffunchelp` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-sys/stores
Description: 共享状态管理库
Latest version: 0.0.6

# @gsp-sys/stores

共享状态管理库，基于Pinia实现，为微应用框架提供统一的状态管理解决方案。

## 导出的Store

### useTabsStore

标签页管理Store，用于管理应用中的标签页状态。

**状态：**
- `activeTab` - 当前激活的标签页
- `tabsList` - 所有标签页列表
- `installAppMap` - 已安装的应用映射
- `keepAliveList` - 需要保持状态的页面
- `globalData` - 全局数据，包括：
  - `number` - 数值
  - `showTabBar` - 是否显示标签栏（仍保留在tabsStore中）


**使用方法：**
```typescript
import { useTabsStore } from '@gsp-sys/stores';

const tabsStore = useTabsStore();

// 获取激活的标签页
const activeTab = tabsStore.activeTab;

// 获取所有标签页
const allTabs = tabsStore.tabsList;

// 获取全局数据
const globalData = tabsStore.globalData;
```

### useContextStore

公共上下文存储，用于管理应用的公共上下文信息，包括国际化和主题变量。

**状态：**
- `currentLocale` - 当前语言代码（'zh'或'en'）
- `primaryColor` - 主题主色
- `globalContextData` - 全局上下文数据，包括：
  - `theme_primary_color` - 主题主色
  - `language` - 当前语言
  - `themeName` - 主题名称
- `isInitialized` - 是否已初始化

**计算属性：**
- `locale` - 当前语言（别名）
- `primaryColorValue` - 主题主色（别名）
- `globalData` - 全局数据（别名）
- `currentTheme` - 当前主题名称

**方法：**
- `setLocale(locale)` - 设置当前语言
- `updateLanguage(lang)` - 更新语言（兼容原方法名）
- `setPrimaryColor(color)` - 设置主题主色
- `initContext()` - 初始化上下文设置

**使用方法：**
```typescript
import { useContextStore } from '@gsp-sys/stores';

const contextStore = useContextStore();

// 设置语言
contextStore.setLocale('en');

// 更新语言（兼容方法）
contextStore.updateLanguage('zh');

// 设置主题主色
contextStore.setPrimaryColor('#2A87FF');

// 获取当前语言
const currentLang = contextStore.currentLocale;
```

### useUserStore

用户状态Store，用于管理用户相关的状态。

**状态：**
- `userInfo` - 用户信息
- `token` - 认证令牌

**计算属性：**
- `isLoggedIn` - 是否已登录
- `hasRole(role)` - 检查用户是否拥有指定角色

**方法：**
- `login(token, userInfo)` - 登录
- `logout()` - 登出
- `updateUserInfo(info)` - 更新用户信息

**使用方法：**
```typescript
import { useUserStore } from '@gsp-sys/stores';

const userStore = useUserStore();

// 登录
userStore.login('token-value', { id: '1', name: 'User', roles: ['admin'] });

// 检查是否登录
if (userStore.isLoggedIn) {
  // 执行登录后的操作
}

// 检查权限
if (userStore.hasRole('admin')) {
  // 显示管理员功能
}

// 登出
userStore.logout();
```

## 注意事项

- 所有Store都使用Composition API风格定义
- 使用前确保已在应用中正确安装和配置Pinia
- 跨包使用时，确保已通过workspace协议正确安装依赖
npm package: @gsp-sys/sysmgr-common
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.10

# Syscommon

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project syscommon` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project syscommon`.
> Note: Don't forget to add `--project syscommon` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build syscommon` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build syscommon`, go to the dist folder `cd dist/syscommon` and run `npm publish`.

## Running unit tests

Run `ng test syscommon` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-sys/sysmgr-lookup
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.8

# sysmgr-lookup

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project sysmgr-lookup` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project sysmgr-lookup`.
> Note: Don't forget to add `--project sysmgr-lookup` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build sysmgr-lookup` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build sysmgr-lookup`, go to the dist folder `cd dist/sysmgr-lookup` and run `npm publish`.

## Running unit tests

Run `ng test sysmgr-lookup` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-sys/user-language-textbox
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.2

# LanguageTextbox

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project language-textbox` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project language-textbox`.
> Note: Don't forget to add `--project language-textbox` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build language-textbox` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build language-textbox`, go to the dist folder `cd dist/language-textbox` and run `npm publish`.

## Running unit tests

Run `ng test language-textbox` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-timestamp/deltable-config
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.12

# DeltableConfig

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

## Code scaffolding

Run `ng generate component component-name --project deltable-config` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project deltable-config`.
> Note: Don't forget to add `--project deltable-config` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build deltable-config` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build deltable-config`, go to the dist folder `cd dist/deltable-config` and run `npm publish`.

## Running unit tests

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

## 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).
npm package: @gsp-wf/biz-process-api
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.1

# BizProcessApi

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project biz-process-api` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project biz-process-api`.
> Note: Don't forget to add `--project biz-process-api` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build biz-process-api` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build biz-process-api`, go to the dist folder `cd dist/biz-process-api` and run `npm publish`.

## Running unit tests

Run `ng test biz-process-api` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/rtdevkit
Description: - 提供提交审批选择流程组件
Latest version: 1.0.6

# WFRuntimeUI

## 版本更新记录

### 0.0.1
- 提供提交审批选择流程组件

## 使用方法
1. module中从@gsp-wf/rtdevkit导入 WFRuntimeModule
2. 注入Service:WFSubmiteService
3. 调用提交审批方法之后会流程引擎会返回：ExcutionResponse,判断其属性needInteraction是否需要交互：如果不需要交互提交审批完成，执行后续逻辑;否则..
4. 调用Service.excute()


### 0.0.2
- 提供集成审批控件组件
1. npm i @gsp-wf/rtdevkit@Latest
2. 替换node_module/@gsp-wf/rtdevkit 下的文件
3. module中导入WFRuntimeModule
```ts
import { WFRuntimeModule } from '@gsp-wf/rtdevkit';
NgModule({ 
  imports: [WFRuntimeModule]
  })

```
4. 
```html
<wf-workitem-handle [workitemId]="" (actions)="updateActions(actions)" (completed)="completed(success)"></wf-workitem-handle>
```
5. 组件中定义接收btns和完成后事件
```ts
  @ViewChild(WfWorkitemHandleComponent)
  workItemHandle: WfWorkitemHandleComponent;
  /**
   *更新本地操作按钮列表
   */
  updateActions(actions: WorkitemAction) {
    
  }
  /**
   * 审批完成后回调
   */
  completed(sucess: boolean) {
    console.log('审批:' + sucess);
  }

  /**
   * 自定义动作操作
   * @param actionCode 操作编号
   */
   onClick(actionCode: string){
     this.workItemHandle.complete('审批意见');
   }

```
npm package: @gsp-wf/task-action-impl
Description: - 任务办理公共组件
Latest version: 0.0.26

# TaskActionImpl
- 任务办理公共组件

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project task-action-impl` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project task-action-impl`.
> Note: Don't forget to add `--project task-action-impl` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build task-action-impl` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build task-action-impl`, go to the dist folder `cd dist/task-action-impl` and run `npm publish`.

## Running unit tests

Run `ng test task-action-impl` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/task-impl-api
Description: - 任务中心第三方实现接口定义组件
Latest version: 0.0.12

# TaskImplApi
- 任务中心第三方实现接口定义组件

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project task-impl-api` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project task-impl-api`.
> Note: Don't forget to add `--project task-impl-api` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build task-impl-api` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build task-impl-api`, go to the dist folder `cd dist/task-impl-api` and run `npm publish`.

## Running unit tests

Run `ng test task-impl-api` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/task-websocket
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.2

# TaskWebsocket

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project task-websocket` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project task-websocket`.
> Note: Don't forget to add `--project task-websocket` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build task-websocket` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build task-websocket`, go to the dist folder `cd dist/task-websocket` and run `npm publish`.

## Running unit tests

Run `ng test task-websocket` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/ui-comment
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.2.0

# 常用审批意见组件库TaskComment

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## 使用说明 
1.
npm package: @gsp-wf/ui-flowchart
Description: ```ts import { UiFlowchartModule } from '@gsp-wf/ui-flowchart'; ``` ```ts import { Component } from '@angular/core';
Latest version: 1.1.14

# 工作流查看流程图组件
```ts
import { UiFlowchartModule } from '@gsp-wf/ui-flowchart';
```
```ts
import { Component } from '@angular/core';

@Component({
  selector: 'wf-flowchart',
  templateUrl: './task-flowchart.component.html',
  styleUrls: ['./task-flowchart.component.css']
})
export class UIFlowchartComponent {
    private taskId: string;
    @Input()
    set workItemId(workItemId: string) {
        this.taskId = workItemId;
        this.viewFlowChart();
        this.viewBizLogs();
    }
    get workItemId() {
        return this.taskId;
    }
}
```

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project ui-flowchart` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project ui-flowchart`.
> Note: Don't forget to add `--project ui-flowchart` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build ui-flowchart` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build ui-flowchart`, go to the dist folder `cd dist/ui-flowchart` and run `npm publish`.

## Running unit tests

Run `ng test ui-flowchart` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-approval-logs
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.2.13

# WfApprovalLogs

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-approval-logs` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-approval-logs`.
> Note: Don't forget to add `--project wf-approval-logs` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-approval-logs` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-approval-logs`, go to the dist folder `cd dist/wf-approval-logs` and run `npm publish`.

## Running unit tests

Run `ng test wf-approval-logs` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-biz-navigation
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.8

# WfBizNavigation

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-biz-navigation` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-biz-navigation`.
> Note: Don't forget to add `--project wf-biz-navigation` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-biz-navigation` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-biz-navigation`, go to the dist folder `cd dist/wf-biz-navigation` and run `npm publish`.

## Running unit tests

Run `ng test wf-biz-navigation` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-bizlog
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.3

# WfBizlog

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-bizlog` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-bizlog`.
> Note: Don't forget to add `--project wf-bizlog` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-bizlog` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-bizlog`, go to the dist folder `cd dist/wf-bizlog` and run `npm publish`.

## Running unit tests

Run `ng test wf-bizlog` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-bizprocess-lookup
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.8

# WfBizprocessLookup

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-bizprocess-lookup` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-bizprocess-lookup`.
> Note: Don't forget to add `--project wf-bizprocess-lookup` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-bizprocess-lookup` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-bizprocess-lookup`, go to the dist folder `cd dist/wf-bizprocess-lookup` and run `npm publish`.

## Running unit tests

Run `ng test wf-bizprocess-lookup` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-dimension-def
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.11

# WfDimensionDef

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-dimension-def` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-dimension-def`.
> Note: Don't forget to add `--project wf-dimension-def` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-dimension-def` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-dimension-def`, go to the dist folder `cd dist/wf-dimension-def` and run `npm publish`.

## Running unit tests

Run `ng test wf-dimension-def` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-process-editor
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 1.2.9

# WfProcessEditor

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-process-editor` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-process-editor`.
> Note: Don't forget to add `--project wf-process-editor` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-process-editor` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-process-editor`, go to the dist folder `cd dist/wf-process-editor` and run `npm publish`.

## Running unit tests

Run `ng test wf-process-editor` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-process-lookup
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.5

# WfProcessLookup

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-process-lookup` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-process-lookup`.
> Note: Don't forget to add `--project wf-process-lookup` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-process-lookup` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-process-lookup`, go to the dist folder `cd dist/wf-process-lookup` and run `npm publish`.

## Running unit tests

Run `ng test wf-process-lookup` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-process-model
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.8

# WfProcessModel

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-process-model` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-process-model`.
> Note: Don't forget to add `--project wf-process-model` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-process-model` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-process-model`, go to the dist folder `cd dist/wf-process-model` and run `npm publish`.

## Running unit tests

Run `ng test wf-process-model` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gsp-wf/wf-sign
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 0.0.5

# WfSign

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

## Code scaffolding

Run `ng generate component component-name --project wf-sign` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project wf-sign`.
> Note: Don't forget to add `--project wf-sign` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build wf-sign` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build wf-sign`, go to the dist folder `cd dist/wf-sign` and run `npm publish`.

## Running unit tests

Run `ng test wf-sign` to execute the unit tests via [Karma](https://karma-runner.github.io).

## 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).
npm package: @gspwidget-s/common
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 1.7.2

# Common

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

## Code scaffolding

Run `ng generate component component-name --project common` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project common`.
> Note: Don't forget to add `--project common` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build common` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build common`, go to the dist folder `cd dist/common` and run `npm publish`.

## Running unit tests

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

## 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).
npm package: @gspwidget/common
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 1.8.3

# Common

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

## Code scaffolding

Run `ng generate component component-name --project common` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project common`.
> Note: Don't forget to add `--project common` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build common` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build common`, go to the dist folder `cd dist/common` and run `npm publish`.

## Running unit tests

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

## 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).
npm package: @gspwidget/dashboard-core
Description: ## CHANGE LOG
Latest version: 0.0.4

# DashboardCore

## CHANGE LOG

0.0.4
- fix(gridster): 修复gridster宽度比子元素总宽度小而嵌套滚动条问题

0.0.3
- feat(gridster): 增加让gridster总高度跟随gridster item变化特性，通过gridHeightReal控制

0.0.2 
- fix: 导出更多必要的 public-api
npm package: @gspwidget/funcs-selector
Description: ![image-20201119141235294](https://cdn.jsdelivr.net/npm/@gspwidget/funcs-selector/doc-img/screenshot.png) <!--  ![image-20201119141235293](https://cdn.jsdelivr.net/npm/@farris/ui-charts/img/1.png)
Latest version: 0.0.5

# 功能菜单多选组件 FuncsSelector

![image-20201119141235294](https://cdn.jsdelivr.net/npm/@gspwidget/funcs-selector/doc-img/screenshot.png)
<!-- 
![image-20201119141235293](https://cdn.jsdelivr.net/npm/@farris/ui-charts/img/1.png)

![image-20201119141235293](https://cdn.jsdelivr.net/npm/@farris/ui-charts/img/1.png)

![image-20201119141315825](https://cdn.jsdelivr.net/npm/@farris/ui-charts/img/2.png) -->

## 注意事项

仅提供了功能多选组件 FuncsSelectorComponent (lib-funcs-selector) 。

虽然包含了模态框的 header、footer 按钮，但并不包含 modal 弹窗相关的功能（打开、关闭弹窗）；可以用任何 modal 组件/服务库实现弹窗打开，然后订阅 FuncsSelectorComponent  的 confirm, cancel 事件来关闭弹窗。



## 使用

安装

```bash
npm i @gspwidget/funcs-selector
```

引用 NgModule

```
import { FuncsSelectorComponent, FuncsSelectorModule } from 'projects/funcs-selector/src/public-api';

@NgModule({
  entryComponents: [
    FuncsSelectorComponent,
  ],
  imports: [
    FuncsSelectorModule,
  ],
 }
```

使用（拿 ngx-bootstrap/modal 举例）

```typescript
// 用其他 modal 服务打开弹窗
const modalRef = this.modal.show(FuncsSelectorComponent, {
  initialState: {
    initSelectedFuncIds: ['WF0202', 'WF0203'],
    maxSelectedAmount: 8,
    title: 'aa'
  }
})
// 订阅确定、取消点击事件
modalRef.content.confirm.subscribe((selectedFuncs) => {
  console.log('User selected funcs: ' + selectedFucns)
  this.modal.hide()
})
modalRef.content.cancel.subscribe((selectedFuncs) => {
  this.modal.hide()
})
```



## API

### `component` FuncsSelectorComponent

| 属性                         | 类型                              | 说明                   | 默认值     |
| ---------------------------- | --------------------------------- | ---------------------- | ---------- |
| @Input() title               | `string`                          | 标题文字               | '功能选择' |
| @Input() maxSelectedAmount   | `string[] | Observable<string[]>` | 最大能选菜单数量       | []         |
| @Input() initSelectedFuncIds | `number`                          | 初始选中的功能 id 列表 | Infinity   |

| 事件              | 输出类型 | 说明       |
| ----------------- | -------- | ---------- |
| @Output() confirm | Func[]   | 点确定按钮 |
| @Output() cancel  | -        | 点关闭按钮 |



### `interface` Func

| 属性     | 类型     | 说明          |
| -------- | -------- | ------------- |
| id       | `string` | id            |
| name     | `string` | 名称          |
| layer    | `string` | 从1开始的层级 |
| parentId | `string` | 父级 id       |
npm package: @gspwidget/gridster
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Latest version: 1.3.6

# Gridster

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

## Code scaffolding

Run `ng generate component component-name --project gridster` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project gridster`.
> Note: Don't forget to add `--project gridster` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build gridster` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build gridster`, go to the dist folder `cd dist/gridster` and run `npm publish`.

## Running unit tests

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

## 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).
npm package: @gspwidget/portlet
Description: 开箱即用的 iGIX 小部件组件，传入 **部件 id** 来渲染部件。
Latest version: 1.6.0

# Portlet ｜ 小部件

开箱即用的 iGIX 小部件组件，传入 **部件 id** 来渲染部件。

> 此包封装了部件服务数据读取等业务细节。若要脱离 **部件概念**，仅使用 **元部件**，应改用 [`@gspwidget/widget-core`](https://www.npmjs.com/package/@gspwidget/widget-core)，仅封装了元部件加载机制、元部件 API 等，可实现更细粒度控制。



## 使用

1. 安装：

```bash
npm i @gspwidget/portlet
```

2. 引入 `PortletModule`:

```typescript
import { PortletModule } from '@gspwidget/portlet';

@NgModule({
  imports: [
    PortletModule
  ]
})
export class YourModule {}
```

3. 渲染 id 为 portletId 的部件：

```html
<lib-portlet
  [portletId]="portletId"
  >
</lib-portlet>
```

## API

#### lib-portlet

| 属性                   | 类型                    | 描述                                                   | 默认值                                                |
| ------------------------- | ----------------------- | ------------------------------------------------------ | ------------------------------------------------------ |
| [portletId]                 | string                  | 指定当前部件 id。**`portletId` 或 `portlet` 选一个必填**。 | - |
| [portlet]                   | EppPortlet              | 指定当前部件。**`portletId` 或 `portlet` 选一个必填**。 | -   |
| [queryConditions]           | QueryCondition[]        | [Farris 筛选方案](https://www.npmjs.com/package/@farris/component-querycondition)输出的筛选条件。可选。 | - |
| [portletNamesUsingDemoData] | string[]                | 部件名称包含哪些字符时，使用演示数据。可选。 | [] |
| [getCustomizedData]         | () => Observable<any[]> | 若传入，则使用此方法返回的 Observable 对象作为部件接收的数据来源。可选。 | - |

| 事件 | 参数 | 描述                             |
| ---- | ---- | -------------------------------- |
| init | 无   | 元部件加载、组件动态创建完成事件 |
npm package: @gspwidget/widget-core
Description: 元部件接口工具，外部框架使用。 - Systemjs 的版本有坑，现在 widget core 用的版本是 systemjs@0.21.5，但 @>=2 版本与之前不兼容，暂时不能用新的。
Latest version: 1.8.3

# WidgetCore

元部件接口工具，外部框架使用。
- Systemjs 的版本有坑，现在 widget core 用的版本是 systemjs@0.21.5，但 @>=2 版本与之前不兼容，暂时不能用新的。

## CHANGE LOG
1.0.3
- fix: 导出 WidgetDevkitService，与 WidgetService 类相同

1.0.2
- fix: 完全去掉对 widget-devkit 的依赖，以免循环依赖。

1.0.0
- 合并入之前版本的 widget-devkit 包功能。

0.2.6
- fix(widget-core): 导入 BrowserModule 改为 CommonModule，防止用于懒加载时报错问题。

0.2.5
- 配置编辑器：数组结构小调整，去掉数组内重复 label，增加 index；
- 配置编辑器：新增帮助下拉框，可配置 Url 动态获取 options。

0.2.3
- 配置编辑器：text 文本框修复回 blur 时触发变更事件；
- 元部件开发预览项目：解决配置编辑器内修改新元部件属性时报错问题。

0.2.2
- widget-project-preview-page 内 widget-container 加入 assetsBaseUrl 配置，修复元部件开发项目 assetsBaseUrl 不正确问题。

0.2.1
- widget-container 增加 [assetsBaseUrl] 属性，可配置元部件静态文件基路径而非写死。