The ‘raw’ system is a discourse-specific thing, so you won’t find anything about it in the Ember guides.
It looks like it’s pretty deliberate in the core code, so I think it’s safe to use it:
In fact, it doesn’t look like raw outlets have the ability to pass anything like the ‘args’ you find in regular plugin-outlets. So context is the only way to go.
Please do feel free to make core PRs if you feel any useful data is missing in regular plugin outlets. Adding new arguments to outlets is relatively safe, backwards compatible, and has negligable performance impact, so it’s unlikely we’ll refuse.
I’ve also struggled with passing arguments through to plugin outlets. My goal has been to put a plugin outlet on a page and have the outlet get access to all the information the other component references get on that page.
EDIT: I realized the below is probably better for its own topic. I also realized that the main issue I have is importing the actions of a component into a plugin outlet. I’ve asked a question about it here:
Is there a simpler/standard way to successfully pass arguments into a plugin outlet?
If in a template there is the following reference to the composer-action-title component, like this: composer.hbs: