René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow selective disabling of rules per query","articleBody":"### What do you want to change?\r\n\r\nCurrently, the only way to [disable the vetting of rules](https://docs.sqlc.dev/en/stable/howto/vet.html#opting-out-of-lint-rules) for a query is with the `@sqlc-vet-disable` flag.\r\nThe problem with this is that it is an \"all-or-nothing\" approach. When provided, that flag disables the vetting of all rules for the query including some which might be needed.\r\nIt would be good to be able to provide a list of rules to skip, like: \r\n``` sqlc\r\n/* @sqlc-vet-disable sqlc/db-prepare no-exec */\r\n```\r\n\r\nIn this case, only the 2 listed rules in the comment would be skipped, but all others would run.\r\nWhen no rule is provided, the flag should disable all rules in the query, just like the current behaviour, for backwards-compatibility.\r\n\r\n#### Use Case\r\nI have a basic `no-delete-without-where` rule which needs to be disabled for a few queries, but the current way to do that involves skipping all rules for the affected queries.\r\n\r\n### What database engines need to be changed?\r\n\r\nPostgreSQL, MySQL, SQLite\r\n\r\n### What programming language backends need to be changed?\r\n\r\n_No response_","author":{"url":"https://github.com/rhodeon","@type":"Person","name":"rhodeon"},"datePublished":"2024-09-28T21:33:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3619/sqlc/issues/3619"}