gzkx-editor 0.0.0

package/CONTRIBUTING.md

@@ -0,0 +1,104 @@
+# How to contribute
+
+- [Getting help](#getting-help)
+- [Submitting bug reports](#submitting-bug-reports)
+- [Contributing code](#contributing-code)
+
+## Getting help
+
+Community discussion, questions, and informal bug reporting is done on the
+[discuss.ProseMirror forum](http://discuss.prosemirror.net).
+
+## Submitting bug reports
+
+Report bugs on the
+[issue tracker](https://code.haverbeke.berlin/prosemirror/prosemirror/issues).
+Before reporting a bug, please read these pointers.
+
+- The issue tracker is for *bugs*, not requests for help. Questions
+  should be asked on the [forum](http://discuss.prosemirror.net).
+
+- Include information about the version of the code that exhibits the
+  problem. For browser-related issues, include the browser and browser
+  version on which the problem occurred.
+
+- Mention very precisely what went wrong. "X is broken" is not a good
+  bug report. What did you expect to happen? What happened instead?
+  Describe the exact steps a maintainer has to take to make the
+  problem occur. A screencast can be useful, but is no substitute for
+  a textual description.
+
+- A great way to make it easy to reproduce your problem, if it can not
+  be trivially reproduced on the website demos, is to submit a script
+  that triggers the issue.
+
+## Contributing code
+
+Code generated by a language model is not welcome in this project.
+Please don't waste my time with it.
+
+If you want to make a change that involves a significant overhaul of
+the code or introduces a user-visible new feature, create an
+[issue](https://code.haverbeke.berlin/prosemirror/prosemirror/issues/)
+first with your proposal.
+
+- Make sure you have a [Codeberg](https://codeberg.org/user/sign_up)
+  or [GitHub](https://github.com/signup/free) account.
+  
+- Use that to create a [code.haverbeke.berlin
+  account](https://code.haverbeke.berlin/user/login).
+
+- Fork the relevant repository.
+
+- Create a local checkout of the code. You can use the
+  [main repository](https://code.haverbeke.berlin/prosemirror/prosemirror) to
+  easily check out all core modules.
+
+- Make your changes, and commit them
+
+- If your changes are easy to test or likely to regress, add tests in
+  the relevant `test/` directory. Either put them in an existing
+  `test-*.js` file, if they fit there, or add a new file.
+
+- Make sure all tests pass. Run `npm run test` to verify tests pass
+  (you will need Node.js v6+).
+
+- Submit a pull request. Don't put more than one feature/fix in a
+  single pull request.
+
+By contributing code to ProseMirror you
+
+ - Agree to license the contributed code under the project's [MIT
+   license](https://code.haverbeke.berlin/prosemirror/prosemirror/blob/main/LICENSE).
+
+ - Confirm that you have the right to contribute and license the code
+   in question. (Either you hold all rights on the code, or the rights
+   holder has explicitly granted the right to use it like this,
+   through a compatible open source license or through a direct
+   agreement with you.)
+
+### Coding standards
+
+- ES6 syntax, targeting an ES5 runtime (i.e. don't use library
+  elements added by ES6, don't use ES7/ES.next syntax).
+
+- 2 spaces per indentation level, no tabs.
+
+- No semicolons except when necessary.
+
+- Follow the surrounding code when it comes to spacing, brace
+  placement, etc.
+
+- Brace-less single-statement bodies are encouraged whenever they
+  don't impact readability.
+
+- [getdocs-ts](https://code.haverbeke.berlin/marijn/getdocs-ts)-style doc comments
+  above items that are part of the public API.
+
+- When documenting non-public items, you can put the type after a
+  single colon, so that getdocs doesn't pick it up and add it to the
+  API reference.
+
+- ProseMirror does *not* follow JSHint or JSLint prescribed style.
+  Patches that try to 'fix' code to pass one of these linters will not
+  be accepted.

package/LICENSE

@@ -0,0 +1,19 @@
+Copyright (C) 2015-2017 by Marijn Haverbeke <marijn@haverbeke.berlin> and others
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

package/PUBLISH.md

@@ -0,0 +1,286 @@
+# GZKX Editor 发包指南
+
+## 准备工作
+
+### 1. 安装 Node.js 和 npm
+
+确保已安装 Node.js (建议 v16+) 和 npm：
+
+```bash
+node -v
+npm -v
+```
+
+### 2. 配置 npm 镜像（可选）
+
+如果使用国内镜像：
+
+```bash
+npm config set registry https://registry.npmmirror.com
+```
+
+### 3. 登录 npm
+
+```bash
+npm login
+```
+
+按提示输入用户名、密码和邮箱。
+
+## 发包步骤
+
+### 方式一：手动发包
+
+#### 1. 进入要发布的包目录
+
+```bash
+cd model
+```
+
+#### 2. 查看并确认 package.json
+
+确保 version、name、description 等信息正确：
+
+```json
+{
+  "name": "gzkx-editor-model",
+  "version": "1.0.0",
+  "description": "GZKX Editor 文档模型"
+}
+```
+
+#### 3. 构建包
+
+每个包需要先构建：
+
+```bash
+npm run prepare
+# 或手动构建
+npm run build
+```
+
+#### 4. 发布到 npm
+
+```bash
+npm publish --access public
+```
+
+对于 scoped 包（如 @your-scope/package）使用：
+
+```bash
+npm publish --access public
+```
+
+### 方式二：批量发包脚本
+
+在项目根目录创建 `publish-all.sh`：
+
+```bash
+#!/bin/bash
+
+PACKAGES=(
+  "model"
+  "state"
+  "view"
+  "commands"
+  "transform"
+  "keymap"
+  "inputrules"
+  "history"
+  "collab"
+  "gapcursor"
+  "schema-basic"
+  "schema-list"
+  "menu"
+  "example-setup"
+  "markdown"
+  "dropcursor"
+  "search"
+  "changeset"
+  "test-builder"
+)
+
+for pkg in "${PACKAGES[@]}"; do
+  echo "Publishing $pkg..."
+  cd "$pkg"
+  npm publish --access public
+  cd ..
+  echo "$pkg published successfully!"
+done
+
+echo "All packages published!"
+```
+
+运行：
+
+```bash
+chmod +x publish-all.sh
+./publish-all.sh
+```
+
+## 包发布流程详解
+
+### 1. 版本号管理
+
+采用语义化版本 (SemVer)：
+
+- **主版本 (major)**：不兼容的 API 变更
+- **次版本 (minor)**：向后兼容的功能新增
+- **补丁版本 (patch)**：向后兼容的问题修复
+
+```bash
+# 升级补丁版本
+npm version patch
+
+# 升级次版本
+npm version minor
+
+# 升级主版本
+npm version major
+```
+
+### 2. 发布前检查清单
+
+- [ ] 更新 CHANGELOG.md
+- [ ] 更新 version 字段
+- [ ] 运行测试确保没有破坏性变更
+- [ ] 检查 package.json 中的 description、maintainers 等信息
+- [ ] 确认没有敏感信息泄露
+
+### 3. 打标签
+
+```bash
+git add .
+git commit -m "Release v1.0.0"
+git tag -a v1.0.0 -m "Release version 1.0.0"
+git push origin main --tags
+```
+
+## 发布到私有 Registry
+
+### 使用 Verdaccio
+
+1. 全局安装 Verdaccio：
+
+```bash
+npm install -g verdaccio
+```
+
+2. 启动私有 registry：
+
+```bash
+verdaccio
+```
+
+3. 修改 npm 配置指向私有 registry：
+
+```bash
+npm config set registry http://localhost:4873
+```
+
+4. 登录：
+
+```bash
+npm adduser --registry http://localhost:4873
+```
+
+5. 发布到私有 registry：
+
+```bash
+cd model
+npm publish --registry http://localhost:4873
+```
+
+## 常见问题
+
+### 1. 发布失败：need to login
+
+```bash
+npm login
+```
+
+### 2. 发布失败：cannot modify version
+
+已发布的版本不能重复发布，需要升级版本号。
+
+### 3. 权限问题 (403 Forbidden)
+
+确保你有该包的管理权限，或者先创建新的包名。
+
+### 4. scoped 包发布
+
+如果使用 `@gzkx-editor/model` 格式，需要先在 npm 上创建 organization：
+
+```bash
+npm org create gzkx-editor
+```
+
+然后发布：
+
+```bash
+npm publish --access public
+```
+
+## 发布后验证
+
+```bash
+# 查看已发布的包信息
+npm view gzkx-editor-model
+
+# 安装验证
+npm install gzkx-editor-model
+```
+
+## CI/CD 自动发布
+
+可以配合 GitHub Actions 实现自动发布：
+
+```yaml
+# .github/workflows/publish.yml
+name: Publish
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: '18'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm run build
+        working-directory: ./model
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        working-directory: ./model
+```
+
+## 包依赖关系
+
+发布时请按以下顺序发布（从底层到上层）：
+
+1. `gzkx-editor-model` - 无外部依赖
+2. `gzkx-editor-transform` - 依赖 model
+3. `gzkx-editor-state` - 依赖 model, transform, view
+4. `gzkx-editor-view` - 依赖 model, state, transform
+5. `gzkx-editor-commands` - 依赖 model, state, transform
+6. `gzkx-editor-keymap` - 依赖 state
+7. `gzkx-editor-inputrules` - 依赖 state, transform
+8. `gzkx-editor-history` - 依赖 state, transform, view
+9. `gzkx-editor-dropcursor` - 依赖 state, view, transform
+10. `gzkx-editor-gapcursor` - 依赖 keymap, model, state, view
+11. `gzkx-editor-schema-basic` - 依赖 model
+12. `gzkx-editor-schema-list` - 依赖 model, transform, state
+13. `gzkx-editor-menu` - 依赖 state, commands, history
+14. `gzkx-editor-collab` - 依赖 state, history, model, transform
+15. `gzkx-editor-example-setup` - 依赖多个上游包
+16. `gzkx-editor-markdown` - 依赖 model
+17. `gzkx-editor-search` - 依赖 model, state, view
+18. `gzkx-editor-changeset` - 依赖 transform
+19. `gzkx-editor-test-builder` - 依赖 model, schema-basic, schema-list

package/README.md

@@ -0,0 +1,80 @@
+**This repository has moved to https://code.haverbeke.berlin/prosemirror/prosemirror**
+
+# prosemirror
+
+[ [**WEBSITE**](https://prosemirror.net) | [**ISSUES**](https://code.haverbeke.berlin/prosemirror/prosemirror/issues) | [**FORUM**](https://discuss.prosemirror.net) ]
+
+ProseMirror is a well-behaved rich semantic content editor based on
+contentEditable, with support for collaborative editing and custom
+document schemas.
+
+The ProseMirror library consists of a number of separate
+[modules](https://code.haverbeke.berlin/prosemirror/). This repository just
+serves as a central issue tracker, and holds a script to help easily
+check out all the core modules for development.
+
+The [project page](https://prosemirror.net) has more information, a
+number of [examples](https://prosemirror.net/examples/) and the
+[documentation](https://prosemirror.net/docs/).
+
+This code is released under an
+[MIT license](https://code.haverbeke.berlin/prosemirror/prosemirror/src/branch/main/LICENSE).
+There's a [forum](http://discuss.prosemirror.net) for general
+discussion and support requests, and the
+[bug tracker](https://code.haverbeke.berlin/prosemirror/prosemirror/issues)
+is the place to report issues.
+
+**STOP READING HERE IF YOU'RE SIMPLY _USING_ PROSEMIRROR. YOU CAN
+INSTALL THE SEPARATE [NPM
+MODULES](https://www.npmjs.com/search?q=prosemirror-) FOR THAT. THE
+INSTRUCTIONS BELOW ONLY APPLY WHEN _DEVELOPING_ PROSEMIRROR!**
+
+## Setting up a dev environment
+
+Clone this repository, and make sure you have
+[node](https://nodejs.org/en/) installed.
+Next, from the cloned directory run:
+
+    bin/pm install
+
+This will fetch the submodules, install their dependencies, and build
+them.
+
+The `bin/pm` script in this repository provides functionality for
+working with the repositories:
+
+ * `bin/pm build` rebuilds all the modules
+
+ * `bin/pm watch` sets up a process that automatically rebuilds the
+   modules when they change
+
+ * `bin/pm status` prints the git status of all submodules
+
+ * `bin/pm commit <args>` runs `git commit` with the given arguments
+   in all submodules that have pending changes
+
+ * `bin/pm test` runs the (non-browser) tests in all modules
+
+ * `bin/pm push` runs `git push` in all modules
+
+ * `bin/pm grep <pattern>` greps through the source code for the
+   modules for the given pattern
+
+ * `bin/pm dev-start` starts a server that rebuilds the packages
+   whenever their sources change, and exposes the demo (`demo/*`)
+   under a webserver on port 8080
+
+(Functionality for managing releases will be added in the future.)
+
+## Community
+
+Development of ProseMirror happens in the various repositories exposed
+under the [ProseMirror](https://code.haverbeke.berlin/prosemirror/) organization
+on code.haverbeke.berlin. Bugs for core packages are tracked in the [bug
+tracker](https://code.haverbeke.berlin/prosemirror/prosemirror/issues) for the
+meta repository.
+
+We aim to be an inclusive, welcoming community. To make that explicit,
+we have a [code of
+conduct](http://contributor-covenant.org/version/1/1/0/) that applies
+to communication around the project.