You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been pondering ways to reuse the rest_api module in other projects that want to post feedback in a CI workflow.
Abstracting the module into a standalone library would require callback function pointers (and/or possibly trait implementations) to keep cpp-linter algorithms separate from REST API usage. This mainly includes
creating comments' content
the comment marker prefixed to each comment (<!-- cpp linter action -->)
Create bindings for the abstracted library for use in python and/or node.js. Using rust async runtimes (like tokio) in python is not yet officially supported in pyo3 project (see pyo3 docs).
This abstracted library wouldn't be specific to cpp-linter, so I should migrate the library to my own github account.
The text was updated successfully, but these errors were encountered:
I've been pondering ways to reuse the
rest_api
module in other projects that want to post feedback in a CI workflow.Abstracting the module into a standalone library would require callback function pointers (and/or possibly trait implementations) to keep cpp-linter algorithms separate from REST API usage. This mainly includes
<!-- cpp linter action -->
)Additional ideas
Create bindings for the abstracted library for use in
python and/ornode.js. Using rust async runtimes (liketokio
) in python is not yet officially supported in pyo3 project (see pyo3 docs).This abstracted library wouldn't be specific to cpp-linter, so I should migrate the library to my own github account.
The text was updated successfully, but these errors were encountered: