* test: create view collection * feat: view collection class * feat: list view * chore: skip sync view collection * test: should create view collection in difference schema * test: create view collection in collection manager * feat: create view collection by user sql * test: view resourcer * feat: view collection * feat: view collection cannot be added, deleted, or modified * feat: view collection cannot be added, deleted, or modified * feat: view collection cannot be added, deleted, or modified * feat: view collection cannot be added, deleted, or modified * refactor: connect to database view * refactor: sync from database * chore: rename list view sql * chore: list view fields api * chore: create collection without viewName * feat: bring out fields when selecting a view * chore: bring out fields when selecting a view * feat: view field inference class * chore: bring out fields when selecting a view * chore: sync form database view * chore: sync form database view * refactor: view collection local * feat: view get api * feat: database type infer * feat: integer map * chore: remove from in view list * chore: build error * chore: uniq collection * fix: typo * chore: replace collection list source field * fix: destroy view collection * chore: timestamp field map * refactor: interface avalableTypes * refactor: interface avalableTypes * chore: list fields test * refactor: interface avalableTypes * chore: uiSchema response in field source * fix: view query * chore: collection snippet * refactor: view collection support preview * fix: handle field source * fix: typo * fix: configure fileds title * fix: configure fileds title * fix: configure fileds title * fix: sync from databse interface * fix: sync from databse interface * feat: set fields api * fix: sync from databse fix * feat: possibleTypes * chore: fields get * fix: sync from databse * fix: list view test * fix: view test in difference schema * chore: comment * feat: when there is only one source collection, the view is a subset of a Collection * feat: view collection add field * fix: inherit query with schema * fix: test * fix: ci test * fix: test with schema * chore: set pg default search path * chore: mysql test * fix: test with schema * chore: test * chore: action test * chore: view column usage return type * feat: mysql field inference * fix: tableName * chore: node sql parser * fix: sql build * fix: database build * fix: mysql test * feat: view collection uiSchema title * fix: incorrect field source display when switching views * refactor: view collection not allow modify * fix: view collection is allow add, delete, and modify * fix: mysql test * fix: sqlite test * fix: sqlite test * fix: sqlite test * fix: sqlite test * chore: add id field as default target key * style: style improve * feat: load source field options * style: style improve * chore: disable remove column in view collection * chore: support creating view collection with different schemas with the same name * chore: support creating view collection with different schemas with the same name * fix: query view in difference schema * refactor: view collection viewname * fix: query view collection in difference schema * fix: field load * chore: field options * fix: mysql test * fix: uiSchema component error when using a view field in a block * fix: sqlite test * chore: test * fix: dump user views * fix: view collection can be updated and edited in table block * chore: sync from database display last field configuration * chore: loadCollections * chore: sync from database display last field configuration * fix: field options merge issues * style: preview table * fix: view collection is allow using in kanban blocks * refactor: code improve * fix: view collection can be updated an edited in calendar block * chore: disable infer field without interface * feat: preview only shows source or interface fields * fix: test * refactor: locale * feat: sql parser * chore: remove node-sql-parser * fix: yarn.lock * test: view repository * fix: view repository test * chore: console.log * chore: console.log * fix: mysql without schema * fix: mysql without schema * chore: preview with field schema * chore: tableActionInitializers * style: preview style improve * chore: parameter is filter when there is no filterByTk * fix: preview pagination * fix: preview pagination * style: preview table style improve * fix: sync from database loading * chore: preview performance optimization * chore: preview performance optimization * feat: limit & offset * chore: preview performance optimization * test: field with dot column * fix: datetime interface display * fix: missing boolean type * fix: sync * fix: sync from database * style: style improve * style: style improve * style: style improve * chore: preview table * chore: preview table * chore: preview table * fix: styling --------- Co-authored-by: katherinehhh <katherine_15995@163.com> Co-authored-by: chenos <chenlinxh@gmail.com>  | 
			||
|---|---|---|
| .. | ||
| src | ||
| client.d.ts | ||
| client.js | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| README.zh-CN.md | ||
| server.d.ts | ||
| server.js | ||
import
English | 中文
Excel 数据导入插件。
安装激活
内置插件无需手动安装激活。
导入说明
数字类型字段
支持数字和百分比,N/A 或 - 的文案会被过滤掉
| 数字1 | 百分比 | 数字2 | 数字3 | 
|---|---|---|---|
| 123 | 25% | N/A | - | 
转 JSON 之后为
{
  "数字1": 123,
  "百分比": 0.25,
  "数字2": null,
  "数字3": null,
}
布尔类型字段
输入文案支持(英文不区分大小写):
YesYTrue1是NoNFalse0否
| 字段1 | 字段2 | 字段3 | 字段4 | 字段4 | 
|---|---|---|---|---|
| 否 | 是 | Y | true | 0 | 
转 JSON 之后为
{
  "字段1": false,
  "字段2": true,
  "字段3": true,
  "字段4": true,
  "字段5": false,
}
日期类型字段
| DateOnly | Local(+08:00) | GMT | 
|---|---|---|
| 2023-01-18 22:22:22 | 2023-01-18 22:22:22 | 2023-01-18 22:22:22 | 
转 JSON 之后为
{
  "DateOnly": "2023-01-18T00:00:00.000Z",
  "Local(+08:00)": "2023-01-18T14:22:22.000Z",
  "GMT": "2023-01-18T22:22:22.000Z",
}
选择类型字段
选项值和选项标签都可作为导入文案,多个选项之间以以逗号(, ,)或顿号(、)区分
如字段 优先级 的可选项包括:
| 选项值 | 选项标签 | 
|---|---|
| low | 低 | 
| medium | 中 | 
| high | 低 | 
选项值和选项标签都可作为导入文案
| 优先级 | 
|---|
| 高 | 
| low | 
转 JSON 之后为
[
  { "优先级": "high" },
  { "优先级": "low" },
]
中国行政区字段
| 地区1 | 地区2 | 
|---|---|
| 北京市/市辖区 | 天津市/市辖区 | 
转 JSON 之后为
{
  "地区1": ["11","1101"],
  "地区2": ["12","1201"]
}
附件字段
| 附件 | 
|---|
| https://www.nocobase.com/images/logo.png | 
转 JSON 之后为
{
  "附件": [
    {
      "filename": "logo.png",
      "title": "logo.png",
      "extname": ".png",
      "url": "https://www.nocobase.com/images/logo.png"
    }
  ]
}
关系类型字段
多条数据以逗号(, ,)或顿号(、)区分
| 部门/名称 | 分类/标题 | 
|---|---|
| 开发组 | 分类1、分类2 | 
转 JSON 之后为
{
  "部门": [1], // 1 为部门名称为「开发组」的记录 ID
  "分类": [1,2], // 1,2 为分类标题为「分类1」和「分类2」的记录 ID
}
JSON 类型字段
| JSON1 | 
|---|
| {"key":"value"} | 
转 JSON 之后为
{
  "JSON": {"key":"value"}
}
地图几何图形类型
| Point | Line | Polygon | Circle | 
|---|---|---|---|
| 1,2 | (1,2),(3,4) | (1,2),(3,4),(1,2) | 1,2,3 | 
转 JSON 之后为
{
  "Point": [1,2],
  "Line": [[1,2], [3,4]],
  "Polygon": [[1,2], [3,4], [1,2]],
  "Circle": [1,2,3]
}
自定义导入格式
通过 db.registerFieldValueParsers() 方法注册自定义的 ValueParser,如:
import { BaseValueParser } from '@nocobase/database';
class PointValueParser extends BaseValueParser {
  async setValue(value) {
    if (Array.isArray(value)) {
      this.value = value;
    } else if (typeof value === 'string') {
      this.value = value.split(',');
    } else {
      this.errors.push('Value invalid');
    }
  }
}
const db = new Database();
// type=point 的字段导入时,将通过 PointValueParser 解析数据
db.registerFieldValueParsers({
  point: PointValueParser,
});
导入示例
| Point | 
|---|
| 1,2 | 
转 JSON 之后为
{
  "Point": [1,2]
}