Jagster
Septembre 17, 2024, 7:12
1
Je pourrais choisir UX Bug
Alors, qu’est-ce que c’est et pourquoi est-ce là :
1 « J'aime »
mcwumbly
Septembre 17, 2024, 8:28
2
Ça ressemble à un bug !
Probablement introduit ici :
main ← ux/convert-chat-plugin-ui
opened 06:19AM - 29 Aug 24 UTC
This commit converts the current chat plugin UI into the
new "show plugin" UI a… lready followed by AI and Gamification:
In the process, I also:
* Made a dedicated /new route to create new webhooks
* Converted the webhook form to FormKit
* Made some fixes and improvements to the `AdminPluginConfigPage`, `AdminPageHeader`,
and `AdminPageSubheader` generic components, so more plugins can
adopt the UI guidelines too. This includes adding a header outlet so plugins
can add action buttons to the plugin show page header.
* Fixes the submit button loading state for FormKit (by Joffrey)
Je le vois aussi sur la page de gamification.
2 « J'aime »
j.jaffeux
Octobre 1, 2024, 12:58
5
Je pense que cela a été corrigé par :
committed 04:35AM - 30 Sep 24 UTC
In 61c1d35f17468b3666c966839da911d9f96dad19 I added a
PluginOutlet to AdminPlug… inConfigPage. This was intended to be
used as a way to render actions buttons inside the header of
a plugin that has a custom admin UI page. This worked, but
since the outlet was generically named, as soon as one plugin
used it the button would show on all plugins.
This fixes the immediate issue by naming the outlet based
on the plugin, then having each plugin specify their own
outlet to render into. There may be a nicer way to do this,
but for now this stops the bleeding.
(pour information @martin )
Merci !
5 « J'aime »
j.jaffeux
Octobre 4, 2024, 12:59
6
Ce sujet a été automatiquement fermé 3 jours après la dernière réponse. Les nouvelles réponses ne sont plus autorisées.
