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

Create standalone lint tool for rpc-config files #9188

Open
ben-grande opened this issue May 2, 2024 · 0 comments
Open

Create standalone lint tool for rpc-config files #9188

ben-grande opened this issue May 2, 2024 · 0 comments
Labels
C: other P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@ben-grande
Copy link

How to file a helpful issue

The problem you're addressing (if any)

The Qrexec Policy has a standalone lint tool, the rpc-config doesn't. It is very valuable to be able to lint a file at will instead of debugging, watching logs during runtime.

Initially discussed at #9176 (comment).

The solution you'd like

Create a rpc-config linter.

The value to a user, and who that user might be

  • Developers that edits the rpc-config configuration will be benefit from this.
  • Developers that modify the parser can verify more easily what the parser accepts.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

@ben-grande ben-grande added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: other P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

No branches or pull requests

2 participants