With new auth plugins now being published, that duplicate sidebar configuration of ff-auth, there is new merit in us moving that logic and behaviour into the core repository.
This would enable all Dashboard users to control client constraints (ie.. specifying a particular connection/user to send a msg to) to all widget types, and not just those users that have the FF Auth plugin.
Another option here is that the sidebar logic (which drives acceptsClientConstraints property on the UI Base config node) only shows when any auth plugin is registered, so we'd then need a way of flagging, from the auth plugin, that they're present
joepavitt
commented
5 months ago
With new auth plugins now being published, that duplicate sidebar configuration of ff-auth, there is new merit in us moving that logic and behaviour into the core repository.
This would enable all Dashboard users to control client constraints (ie.. specifying a particular connection/user to send a
msgto) to all widget types, and not just those users that have the FF Auth plugin.Another option here is that the sidebar logic (which drives
acceptsClientConstraintsproperty on the UI Base config node) only shows when any auth plugin is registered, so we'd then need a way of flagging, from the auth plugin, that they're present