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

integrate plpgsql_check #190

Open
psteinroe opened this issue Jan 31, 2025 · 0 comments
Open

integrate plpgsql_check #190

psteinroe opened this issue Jan 31, 2025 · 0 comments

Comments

@psteinroe
Copy link
Collaborator

psteinroe commented Jan 31, 2025

since we have a db connection, we should be able to integrate plpgsql_check. I would propose two layers:

  1. inline lints on the source code itself: actively query the extension for the function we detect in the source and show lints. we might even be able to show the exact location of the lints within the function body.
  2. list issues in the database unrelated to the source code: show all results for all functions. these lints can get quite long quite fast, so we probably want to allow the user to filter out certain schemas / functions / issues types / error levels.

I would first go with 1), and then try to figure out a good way to do 2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant