eschutho commented on issue #12566:
URL: https://github.com/apache/superset/issues/12566#issuecomment-767236468
> 💯 Even though the plugin API is not yet mature, it is a very important one
so I think it would be wise to bump Superset's major version if we make
breaking changes to that interface.
>
> We also need more thorough documentation of what exactly is included in
the plugin interface in order to really determine if a change to the interface
is breaking for plugins or not. Just because a change doesn't happen to break
our builtin plugins doesn't mean it won't break some third party code
somewhere, so we should start being clearer on what third party code can expect
from Superset.
Thanks @suddjian and @ktmud. Do you have suggestions on what wording for
this interface? I'll start with @ktmud's wording.
Something like:
```
**What is a breaking change?**
- Superset UI
- Any updates to superset-ui and the visual control related code in
superset-frontend that break an existing visual plugin
**Best practices to make changes backward compatible:**
- Superset UI
- ??? Anything we can do here?
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
