|
| 1 | +# openinula README |
| 2 | + |
| 3 | +This is the README for your extension "openinula". After writing up a brief description, we recommend including the following sections. |
| 4 | + |
| 5 | +## Features |
| 6 | + |
| 7 | +Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file. |
| 8 | + |
| 9 | +For example if there is an image subfolder under your extension project workspace: |
| 10 | + |
| 11 | +\!\[feature X\]\(images/feature-x.png\) |
| 12 | + |
| 13 | +> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow. |
| 14 | +
|
| 15 | +## Requirements |
| 16 | + |
| 17 | +If you have any requirements or dependencies, add a section describing those and how to install and configure them. |
| 18 | + |
| 19 | +## Extension Settings |
| 20 | + |
| 21 | +Include if your extension adds any VS Code settings through the `contributes.configuration` extension point. |
| 22 | + |
| 23 | +For example: |
| 24 | + |
| 25 | +This extension contributes the following settings: |
| 26 | + |
| 27 | +* `myExtension.enable`: Enable/disable this extension. |
| 28 | +* `myExtension.thing`: Set to `blah` to do something. |
| 29 | + |
| 30 | +## Known Issues |
| 31 | + |
| 32 | +Calling out known issues can help limit users opening duplicate issues against your extension. |
| 33 | + |
| 34 | +## Release Notes |
| 35 | + |
| 36 | +Users appreciate release notes as you update your extension. |
| 37 | + |
| 38 | +### 1.0.0 |
| 39 | + |
| 40 | +Initial release of ... |
| 41 | + |
| 42 | +### 1.0.1 |
| 43 | + |
| 44 | +Fixed issue #. |
| 45 | + |
| 46 | +### 1.1.0 |
| 47 | + |
| 48 | +Added features X, Y, and Z. |
| 49 | + |
| 50 | +--- |
| 51 | + |
| 52 | +## Following extension guidelines |
| 53 | + |
| 54 | +Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension. |
| 55 | + |
| 56 | +* [Extension Guidelines](https://code.visualstudio.com/api/references/extension-guidelines) |
| 57 | + |
| 58 | +## Working with Markdown |
| 59 | + |
| 60 | +You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts: |
| 61 | + |
| 62 | +* Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux). |
| 63 | +* Toggle preview (`Shift+Cmd+V` on macOS or `Shift+Ctrl+V` on Windows and Linux). |
| 64 | +* Press `Ctrl+Space` (Windows, Linux, macOS) to see a list of Markdown snippets. |
| 65 | + |
| 66 | +## For more information |
| 67 | + |
| 68 | +* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown) |
| 69 | +* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/) |
| 70 | + |
| 71 | +**Enjoy!** |
| 72 | +# inula2-vscode-plugin |
| 73 | + |
| 74 | +#### 介绍 |
| 75 | +openInula2.0的VSCode插件,能够在开发过程中为开发者提供组件信息、标识状态、响应关系等。 |
| 76 | + |
| 77 | +#### 软件架构 |
| 78 | +软件架构说明 |
| 79 | + |
| 80 | + |
| 81 | +#### 安装教程 |
| 82 | + |
| 83 | +1. xxxx |
| 84 | +2. xxxx |
| 85 | +3. xxxx |
| 86 | + |
| 87 | +#### 使用说明 |
| 88 | + |
| 89 | +1. xxxx |
| 90 | +2. xxxx |
| 91 | +3. xxxx |
| 92 | + |
| 93 | +#### 参与贡献 |
| 94 | + |
| 95 | +1. Fork 本仓库 |
| 96 | +2. 新建 Feat_xxx 分支 |
| 97 | +3. 提交代码 |
| 98 | +4. 新建 Pull Request |
| 99 | + |
| 100 | + |
| 101 | +#### 特技 |
| 102 | + |
| 103 | +1. 使用 Readme\_XXX.md 来支持不同的语言,例如 Readme\_en.md, Readme\_zh.md |
| 104 | +2. Gitee 官方博客 [blog.gitee.com](https://blog.gitee.com) |
| 105 | +3. 你可以 [https://gitee.com/explore](https://gitee.com/explore) 这个地址来了解 Gitee 上的优秀开源项目 |
| 106 | +4. [GVP](https://gitee.com/gvp) 全称是 Gitee 最有价值开源项目,是综合评定出的优秀开源项目 |
| 107 | +5. Gitee 官方提供的使用手册 [https://gitee.com/help](https://gitee.com/help) |
| 108 | +6. Gitee 封面人物是一档用来展示 Gitee 会员风采的栏目 [https://gitee.com/gitee-stars/](https://gitee.com/gitee-stars/) |
0 commit comments