Gajus Kuizinas

Example implementation: ```ts import { sql, type IdentifierSqlToken, type QueryResultRow, type SqlSqlToken, type SqlToken, } from 'slonik'; import { type z, type ZodTypeAny, } from 'zod'; type ColumnIdentifiers = Record;...

This should also throw an error if keys are duplicate.

The reason this has remained an open issue is because it feels like an overly specialised feature, that likely better belongs in an abstraction such as https://github.com/gajus/slonik-utilities

The logic for handling normalization of keys is because ESLint may enforce `id-match` rule. The same reason does not apply for unique constraints. In some thread it was even discussed...

Interesting. I like this. Will patch it up.

Yup, I've dropped `express-jsonschema` from production because of this issue.

Does anyone have a one-liner workaround to enforce required parameters?

Thanks @anukul , I was more wondering if there a way to write generic check, e.g. using JavaScript actions. However, it seems that it is impossible to get parent inputs.

@anukul Looks like your suggestion doesn't work either. At least in composite actions, env does not include `INPUT_`. https://github.com/actions/runner/issues/665

Something like this works: ```yaml - run: | [[ "${{ inputs.docker_image_name }}" ]] || { echo "docker_image_name input is empty" ; exit 1; } [[ "${{ inputs.doppler_token }}" ]] ||...