terrymanu opened a new issue, #19241: URL: https://github.com/apache/shardingsphere/issues/19241
The contents of dev-manual is not clear enough, I just provide the template of the contents: For each SPI: ``` ## SPI Class Name ### Fully-qualified class name [`org.apache.shardingsphere.xxx.XXX`](https://github.com/apache/shardingsphere/blob/master/xxx/xxx/XXX.java) ### Definition [Definition descriptions] ### Implementation classes | *Configuration Type* | *Description* | *Fully-qualified class name* | | --------------------- | ------------------ | ---------------------------- | | XXX | description details | [`org.apache.shardingsphere.xxx.xxx.XXX`](https://github.com/apache/shardingsphere/blob/master/xxx/xxx/XXX.java) | ``` The English examples please reference [agent.en.md](https://github.com/apache/shardingsphere/blob/master/docs/document/content/dev-manual/agent.en.md) and [configuration.en.md](https://github.com/apache/shardingsphere/blob/master/docs/document/content/dev-manual/configuration.en.md) The Chinese examples please reference [agent.cn.md](https://github.com/apache/shardingsphere/blob/master/docs/document/content/dev-manual/agent.cn.md) and [configuration.cn.md](https://github.com/apache/shardingsphere/blob/master/docs/document/content/dev-manual/configuration.cn.md) The documents need to be updated are: - [ ] mode.en.md and mode.cn.md - [ ] kernel.en.md and kernel.cn.md - [ ] data-source.en.md and data-source.cn.md - [ ] sql-parser.en.md and sql-parser.cn.md - [ ] proxy.en.md and proxy.cn.md - [ ] sharding.en.md and sharding.cn.md - [ ] readwrite-splitting.en.md and readwrite-splitting.cn.md - [ ] ha.en.md and ha.cn.md - [ ] transaction.en.md and transaction.cn.md - [ ] sql-check.en.md and sql-check.cn.md - [ ] encrypt.en.md and encrypt.cn.md - [ ] shadow.en.md and shadow.en.md -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
