feat(codegen): emit nullable.Value[T] when nullable-type is enabled#2067
feat(codegen): emit nullable.Value[T] when nullable-type is enabled#2067frenchi wants to merge 1 commit into
nullable-type is enabled#2067Conversation
- Switch generator to output nullable.Value[T] for nullable fields - Update schema tests to expect Value[T] - Update README to prefer nullable.Value with migration notes - Do not edit generated fixtures; regeneration will follow after library update Notes: - Requires nullable library release containing Value[T] - Regenerate test fixtures after bumping dependency Refs: oapi-codegen/nullable#21 Pending: oapi-codegen/nullable#21
Kusari Analysis Results:
Both dependency and code security analyses completed successfully with no critical security concerns identified. The new dependency github.com/oapi-codegen/nullable@1.1.0 originates from the same organization, has no known vulnerabilities, uses a permissive license, and is at the latest version. While the dependency shows low maintenance activity, this represents a development practice concern rather than a security risk, especially given the organizational relationship. The code analysis found no security vulnerabilities, exposed secrets, or other security issues. The combined risk profile remains low with appropriate mitigations focused on ongoing monitoring rather than blocking deployment. Expand to see all dependency changes, security advisories, scorecard checks, etc.Dependency Changes Introduced
Scorecard Checksgithub.com/oapi-codegen/nullable:
Files where issues may be foundDependency Files:
Found this helpful? Give it a 👍 or 👎 reaction! |
Follow-on PR from oapi-codegen/nullable#21.
Please do not merge this before nullable/pull/21 lands (tests won't pass anyway).
nullable.Nullable[T]to outputnullable.Value[T]for nullable fieldsBefore merging this PR, and after nullable/pull/21 lands:
go get github.com/oapi-codegen/nullablego generate ./internal/test/issues/issue-1039(and other fixtures) to re-emitnullable.Value[...].