You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shardingsphere.apache.org by Nianjun Sun <su...@apache.org> on 2023/07/31 01:34:24 UTC
Plan to remove the SPI in dev manual
As we can see, there are some SPIs in dev manual(
https://shardingsphere.apache.org/document/current/en/dev-manual/), however
only the SPI related to API is meaningful for developer, so we plan to
remove the developer manual except for the algorithm.
Best regards,
Nianjun
——————————————————————
Nianjun Sun(sunnianjun@apache.org)
Apache ShardingSphere Committer
GitHub@taojintianxia
Re: Plan to remove the SPI in dev manual
Posted by "zhangliang@apache.org" <zh...@apache.org>.
+1
Indeed, it is meaningless to expose too many implementation details in the
document.
Only the SPIs that require user configuration have practical value.
It is sufficient to retain the SPIs for the algorithms at present.
------------------
Sincerely,
Liang Zhang (John)
Apache ShardingSphere
Nianjun Sun <su...@apache.org> 于2023年7月31日周一 09:34写道:
> As we can see, there are some SPIs in dev manual(
> https://shardingsphere.apache.org/document/current/en/dev-manual/),
> however
> only the SPI related to API is meaningful for developer, so we plan to
> remove the developer manual except for the algorithm.
>
> Best regards,
> Nianjun
> ——————————————————————
> Nianjun Sun(sunnianjun@apache.org)
> Apache ShardingSphere Committer
> GitHub@taojintianxia
>