Skip to content

Conversation

@GuiLeme
Copy link
Collaborator

@GuiLeme GuiLeme commented Feb 19, 2025

What does this PR do?

It basically simplifies all the samples, now we have each of them with specific role of testing a single feature of the plugin API (Overall this wasn't a big of a change... Because most of the samples already followed that pattern). The directives now are:

  • One sample for each extensible area, because they are visual;
  • One sample for each of the other pluginAPIs (and only one) - that is data-consumption-hook, ui-commands, server-commands, ui-events, dom-element-manipulation and so on;

Besides that, I also updated the packages and npm audit fix the ones that needed.

Motivation

With this new way of doing the samples, a novice plugin dev won't find it hard to test and see each functionality working separately. This way, we decrease the learning curve for the plugins.

@antobinary
Copy link
Member

Should we still be targeting main or should we point to v0.0.x?

@antobinary antobinary merged commit b8a6f7b into bigbluebutton:main Feb 25, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants