Decompose core-API and enhanced-API.

[kevinten10]

Now all API definitions are together, like dapr.proto.

Do we need to decompose it? Otherwise, with more and more APIs, this client will expand more, but in fact, many APIs not core.

If we want to push the API into a unified standard, but in many cases, everyone will add some of their own unique implementations. At this time, it is not appropriate to put it in the core API.

I don’t know how the community views this issue?

The same discussion is in #mosn/layotto#194.

[kevinten10]

I did a split attempt in https://github.com/reactivegroup/cloud-runtimes-jvm

[yaron2]

Take a look at the issue here: #2817

Basically we're considering separating out the Dapr APIs from the implementation at some point. If that comes to pass, I imagine something like a Core API group might make sense. Feel free to join in the discussion in #2817.

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[dapr-bot]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.