Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

abstract rest_api module into a seperate library #97

Open
4 tasks
2bndy5 opened this issue Jan 14, 2025 · 0 comments
Open
4 tasks

abstract rest_api module into a seperate library #97

2bndy5 opened this issue Jan 14, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@2bndy5
Copy link
Collaborator

2bndy5 commented Jan 14, 2025

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

Additional ideas

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.

@2bndy5 2bndy5 added the enhancement New feature or request label Jan 14, 2025
@2bndy5 2bndy5 self-assigned this Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant