This is an automated email from the ASF dual-hosted git repository.
EnxDev pushed a change to branch enxdev/feat/chatbot-context-sharing
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 2223cc3e54a feat(extensions): context sharing namespaces (navigation,
explore, dashboard, dataset)
discard 6bd550e5022 feat(extensions): backend settings persistence and
admin-only permissions
discard 8d8a4dbf065 feat(extensions): admin configuration UI for extensions
discard 1bf86dfd8f2 feat(extensions): eager-load extensions at app-shell
startup
discard 5e98ff968df feat(extensions): define the chatbot entry point in the
frontend API
add f8e7ee9dc23 feat(extensions): define the chatbot entry point in the
frontend API
add 7c9efd529be feat(extensions): eager-load extensions at app-shell
startup
add 197e14de1b3 feat(extensions): admin configuration UI for extensions
add 8b52fff57b4 feat(extensions): backend settings persistence and
admin-only permissions
add 8f03c5a1eae feat(extensions): context sharing namespaces (navigation,
explore, dashboard, dataset)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (2223cc3e54a)
\
N -- N -- N refs/heads/enxdev/feat/chatbot-context-sharing
(8f03c5a1eae)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
superset-frontend/src/core/views/index.ts | 11 +++++-
.../src/extensions/ExtensionsStartup.tsx | 8 ++--
superset/extensions/settings.py | 43 +++++++++++++++++++---
3 files changed, 50 insertions(+), 12 deletions(-)
