:wave: I already posted it in <#C07UNDEAF6K|> but ...
# community-support
r
👋 I already posted it in #C07UNDEAF6K but also reposting it here with the hope of quick response - if anyone had already tried it in their project/application. > Just getting started with problems api. Was wondering the scope it, can it be used to catch any errors thrown during the build by any task. > > If my understanding is correct, it can be directly used by plugin authors, change the way they throw errors in their custom tasks using the problemId they create in their custom tasks and then to be used by the their reporter. > > If you have to use the problem's api to have rich error messaging, append stuff in scans, integrate with IDE tooling etc.., in an application or in a consumer project - some kind of build-listeners needs to be used or something similar, hooked with problem-api?
I am considering utilising the problem’s API to provide more descriptive and detailed messaging whenever any task is executed in the application, such as
clean
,
assemble
,
check
, etc. and I plan to catch a few specific exceptions, such as
UnknownHostException
, and throw custom messages that leverage the problem reporter, with detailed messages, references to relevant documentation, to guide users in resolving any issues. etc...