Go to file
被雨水过滤的空气-Rairn e27cff15c9
feat: support to-multi field variables (#1680)
* feat: support to parse association variable

* chore: change comment

* feat(operators): support array as value in string operator

* refactor: add a special marker

* feat: date support to-multi field variables

* feat: support for notIn

* refactor: rename

* test: fix test error

* Revert "test: fix test error"

This reverts commit 3d139698f6295678a39b77b08c88427f9fafe247.

* Revert "refactor: rename"

This reverts commit 2e16225c038e18ee25f1136d510cb4746bd9932f.

* Revert "feat: support for notIn"

This reverts commit 2087e5c4da1429b260890d5136c714ad541955a9.

* Revert "feat: date support to-multi field variables"

This reverts commit 0d7b2db0512ba7b632a2ab61f37cf83c0d06b9a1.

* Revert "refactor: add a special marker"

This reverts commit 7ba2e4bc00d79f60a2e90340df65b2938985750a.

* Revert "feat(operators): support array as value in string operator"

This reverts commit 0897cd19e9863248ef9e2af6c91ee14e805778a4.

* refactor: improve code

* test: fix can not import style file

* feat: only eq and ne oprators support mutil relation fields

* test: add example.test.ts

* refactor: remove jsonata

* Revert "test: add example.test.ts"

This reverts commit 0ad2ea458cd8a964891490d2021a5b000f391395.

* test: fix error

* fix: fix error

* refactor: remove async

* chore: rebase

* test: fix error

* test: fix errors
2023-05-21 17:18:35 +08:00
__mocks__ feat: support to-multi field variables (#1680) 2023-05-21 17:18:35 +08:00
.github chore(github-template): clean comments and format (#1878) 2023-05-17 17:21:21 +08:00
.vscode feat: support file collection (#1636) 2023-04-06 12:43:40 +08:00
docker fix: cache with index.html (#1541) 2023-03-06 12:00:12 +08:00
docs chore: update changelog 2023-05-11 12:52:35 +08:00
examples fix: eslint (#1759) 2023-04-25 13:12:14 +08:00
packages feat: support to-multi field variables (#1680) 2023-05-21 17:18:35 +08:00
storage fix: yarn start error in windows system (#1177) 2022-12-02 14:23:07 +08:00
.buildrc.ts feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
.editorconfig Feat: client base entry of plugin workflow (#225) 2022-03-27 15:51:48 +08:00
.env.example feat(plugin-workflow): add workflow specific logger (#1677) 2023-04-10 06:00:29 -07:00
.env.test.example fix: yarn start error in windows system (#1177) 2022-12-02 14:23:07 +08:00
.eslintignore fix: eslint (#1759) 2023-04-25 13:12:14 +08:00
.eslintrc chore: cleanup 2023-04-26 22:32:45 +08:00
.gitignore feat: multiple apps (#1540) 2023-03-10 19:16:00 +08:00
.gitpod.yml chore: gitpod yml 2023-02-15 14:47:02 +00:00
.prettierignore feat: translation 2022-05-01 11:09:22 +08:00
.prettierrc refactor: code splitting of the table component (#121) 2021-12-02 22:56:16 +08:00
.umirc.ts feat: update docs (#996) 2022-10-31 22:41:24 +08:00
CHANGELOG.md chore: update changelog 2023-05-11 12:52:35 +08:00
commitlint.config.js fix: eslint (#1759) 2023-04-25 13:12:14 +08:00
docker-compose.yml feat: database view collection (#1587) 2023-04-01 21:56:01 +08:00
Dockerfile chore: update dockerfile (#1754) 2023-04-24 14:27:11 +08:00
Dockerfile.acr chore: update dockerfile (#1754) 2023-04-24 14:27:11 +08:00
jest.config.js feat: support to-multi field variables (#1680) 2023-05-21 17:18:35 +08:00
jest.setup.ts test: should load the .env.test (#1678) 2023-04-10 08:48:26 +08:00
jest.setupAfterEnv.ts test: should load the .env.test (#1678) 2023-04-10 08:48:26 +08:00
lerna.json chore(versions): 😊 publish v0.9.3-alpha.1 2023-05-11 12:49:18 +08:00
LICENSE-AGPL feat: change license (#1350) 2023-01-11 11:58:47 +08:00
LICENSE-APACHE-2.0 feat: change license (#1350) 2023-01-11 11:58:47 +08:00
package.json fix: eslint (#1759) 2023-04-25 13:12:14 +08:00
README.md Update README.md 2023-03-07 12:30:19 +08:00
README.tr-TR.md feat: change license (#1350) 2023-01-11 11:58:47 +08:00
README.zh-CN.md Update README.zh-CN.md 2023-03-07 12:31:08 +08:00
tsconfig.jest.json feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
tsconfig.json chore: cleanup 2023-04-26 22:32:45 +08:00
tsconfig.server.json feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
yarn.lock feat: support reboot application manually (#1889) 2023-05-19 20:34:22 +08:00

English | 中文 | Türkçe

Note: 📌

NocoBase is in early stage of development and is subject to frequent changes, please use caution in production environments.

We are hiring

We are looking for full-time, remote product design and development colleagues to join the team. If you have a strong interest in NocoBase, please feel free to email us at hello@nocobase.com.

What is NocoBase

NocoBase is a scalability-first, open-source no-code development platform. No programming required, build your own collaboration platform, management system with NocoBase in hours.

Homepage:
https://www.nocobase.com/

Online Demo:
https://demo.nocobase.com/new

Documents:
https://docs.nocobase.com/

Contact Us:
hello@nocobase.com

Who is NocoBase for

NocoBase is designed for you if you have the following needs.

  • Develop an internal management system
  • Meet most of your business needs with no-code development
  • No-code development is simple enough for non-developers; flexible enough to be close to native development
  • Can be very easy to extend
  • Private deployment with full control of code and data
  • Free to use or pay for more technical support

Why NocoBase is different

1. Separate "data structure" and "user interface"

Most form-, table-, or process-driven codeless products create data structures directly in the user interface, such as Airtable, where adding a new column to a table is adding a new field. This has the advantage of simplicity of use, but the disadvantage of limited functionality and flexibility to meet the needs of more complex scenarios.

NocoBase adopts the design idea of separating the data structure from the user interface, allowing you to create any number of blocks (data views) for the data collections, with different type, styles, content, and actions in each block. This takes into account the simplicity of codeless operation, but also the flexibility like native development.

2.collection-block.png

2. What you see is what you get

NocoBase enables the development of complex and distinctive business systems, but this does not mean that complex and specialized operations are required. With a single click, configuration options can be displayed on the usage interface, which means that administrators with system configuration rights can configure the user interface directly with WYSIWYG operations.

2.user-root.gif

3. Everything is a plugin

NocoBase adopts plugin architecture, all new features can be implemented by developing and installing plugins. In the future, we will build a plug-in marketplace where extending functionality is as easy as installing an APP on your phone.

Click to view the full image

Business Services

If you need commercial version and commercial services, please feel free to contact us by email: hello@nocobase.com

Also by WeChat

Installation

NocoBase supports three installation methods:

  • Installing With Docker (👍Recommended)

    Suitable for no-code scenarios, no code to write. When upgrading, just download the latest image and reboot.

  • Installing from create-nocobase-app CLI

    The business code of the project is completely independent and supports low-code development.

  • Installing from Git source code

    If you want to experience the latest unreleased version, or want to participate in the contribution, you need to make changes and debug on the source code, it is recommended to choose this installation method, which requires a high level of development skills, and if the code has been updated, you can git pull the latest code.

License