New Plugin Outlet in Chat Plugin

AI-generated summary

The discussion revolves around adding a plugin outlet to the Channel settings page in the Chat Plugin, specifically for introducing additional navigation tabs. merefield proposes adding a new route and UI component, but david notes that chat routes are unusual due to their lack of URL-based routing, making standard route extensions ineffective. merefield clarifies that a self-contained component with data retrieval would suffice, but the current plugin API doesn’t support this. j.jaffeux acknowledges the lack of a robust extension system and states that they currently lack the bandwidth to develop a maintainable solution, emphasizing the need to consider various use cases.

I would like to add some functionality on the Channel settings page, any objection to PRing a Nav plugin outlet here?:

In similar vein to Group Nav

Do you just plan to put a link there? Or are you hoping to add a full tab with its own UI?

The groups page is slightly different in that sense, because each tab is its own controller/route. That’s not the case for chat settings.

Glad you raised that!

Yes, I’d like to put in my own route with associated functionality.

But of course, that would mean?:

  • creating an additional route
  • altering the existing route map?
  • extending the existing ChannelInfoNav?
  • adding a new Component

Is that not feasible with the current plugin API?

This in general would be a useful thing to be able to do on similar Nav bars.

Chat routes are a little unusual, because they’re not always ‘real routes’. e.g. if you open chat in the popout UI, the settings tabs still work, but don’t change the actual browser URL.

So, I don’t think defining a new route in your plugin/theme will be enough.

@j.jaffeux I think you’re most familiar with this stuff. What do you think we’d need to permit themes/plugins to introduce additional tabs to channel settings? :thinking:

Yeah, it’s kind of a widget, so no URL routes :thinking:

I’m not hung up on adding a route if we can somehow achieve UI extension with self contained Components that are responsible for their own data retrieval.

But yeah, then I’d need an api to extend the navigation bar which would allow me to bring up a Component of my specification …

Sorry but yes we don’t have a good extension story for this and don’t have the bandwidth to come up with something for now. I will need to think of all the cases to provide a solution Im comfortable maintaining.