Hey again. I've been playing with `FlowAction` to ...
# plugin-development
j
Hey again. I've been playing with
FlowAction
to analyze exceptions thrown by builds to try and report problems using them. I noticed that I can't inject the
Problems
service to them, but I can inject it into
FlowParameters
. It's rather strange but it works. Is there any sort of intentional way to use the problems API within a dataflow action? Or has it just not been implemented yet and is planned?
m
FlowAction
is still an incubating feature, and we want to make some changes to
FlowParameters
handling soon enough. I'm not sure if we'll have to sacrifice passing services like
Problems
through parameters, but this is a possibility, so I wouldn't recommend relying on in this feature in something hard to update, like a plugin published to the Gradle Plugin Portal. Hopefully, we'll finalize everything by Gradle 9.0. Can you please file an issue describing your request? It will help to keep the use case on our radar.
j
Roger that. I'll file the issue when I'm back home. The plugin I'm working on is meant to be targeting Gradle 9.0, which is why I am playing around with incubating features like this even though it's on Gradle 8.14.
Honestly it would be ideal if Problems could be injected globally
Sorry, I've had a busy week. When I'm back home in a few hours I will write up a small project that shows my use case and make an issue on the GitHub.