Title: Support `undefined`, `number` in JSON module by mario-campos · Pull Request #3980 · github/codeql-action · GitHub
Open Graph Title: Support `undefined`, `number` in JSON module by mario-campos · Pull Request #3980 · github/codeql-action
X Title: Support `undefined`, `number` in JSON module by mario-campos · Pull Request #3980 · github/codeql-action
Description: Summary This pull request introduces several additions to the JSON schema-validation utilities: Renamed the optional validator to optionalOrNull to clarify that schema fields may be optional and accept null as a valid value, in addition to undefined. Redefined the optional validator so that it only accepts undefined (not null), making its behavior more precise and distinct from optionalOrNull. Added new built-in validators for number. Added an isNumber type guard function for type checking. This PR is a prerequisite for #3950. Risk assessment For internal use only. Please select the risk level of this change: Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only. Which use cases does this change impact? Workflow types: Advanced setup - Impacts users who have custom CodeQL workflows. Managed - Impacts users with dynamic workflows (Default Setup, Code Quality, ...). Products: Code Scanning - The changes impact analyses when analysis-kinds: code-scanning. Code Quality - The changes impact analyses when analysis-kinds: code-quality. Environments: Dotcom - Impacts CodeQL workflows on github.com and/or GitHub Enterprise Cloud with Data Residency. GHES - Impacts CodeQL workflows on GitHub Enterprise Server. How did/will you validate this change? Unit tests - I am depending on unit test coverage (i.e. tests in .test.ts files). End-to-end tests - I am depending on PR checks (i.e. tests in pr-checks). If something goes wrong after this change is released, what are the mitigation and rollback strategies? Rollback - Change can only be disabled by rolling back the release or releasing a new version with a fix. How will you know if something goes wrong after this change is released? Telemetry - I rely on existing telemetry or have made changes to the telemetry. Alerts - New or existing monitors will trip if something goes wrong with this change. Are there any special considerations for merging or releasing this change? No special considerations - This change can be merged at any time. Merge / deployment checklist Confirm this change is backwards compatible with existing workflows. Consider adding a changelog entry for this change. Confirm the readme and docs have been updated if necessary.
Open Graph Description: Summary This pull request introduces several additions to the JSON schema-validation utilities: Renamed the optional validator to optionalOrNull to clarify that schema fields may be optional and a...
X Description: Summary This pull request introduces several additions to the JSON schema-validation utilities: Renamed the optional validator to optionalOrNull to clarify that schema fields may be optional and a...
Opengraph URL: https://github.com/github/codeql-action/pull/3980
X: @github
Domain: github.com
| route-pattern | /:user_id/:repository/pull/:id/files(.:format) |
| route-controller | pull_requests |
| route-action | files |
| fetch-nonce | v2:8987a5a7-449e-c3a9-ec2b-03b3660315ea |
| current-catalog-service-hash | ae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b |
| request-id | 8A12:35ABFC:134EE0C:1B8199F:6A4CC178 |
| html-safe-nonce | ab3dfa40c96fabb6e7d64f1889284198981f291d9213b23543f95f45b12b490b |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4QTEyOjM1QUJGQzoxMzRFRTBDOjFCODE5OUY6NkE0Q0MxNzgiLCJ2aXNpdG9yX2lkIjoiNTAyMjA4ODQwNzU0NDU0NTY1NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | a7460af2d2307232bb24204100b0f6322ccad7db9f96098e54b7af5f25400d8a |
| hovercard-subject-tag | pull_request:3966516903 |
| github-keyboard-shortcuts | repository,pull-request-list,pull-request-conversation,pull-request-files-changed,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/github/codeql-action/pull/3980/files |
| twitter:image | https://avatars.githubusercontent.com/u/1663284?s=400&v=4 |
| twitter:card | summary_large_image |
| og:image | https://avatars.githubusercontent.com/u/1663284?s=400&v=4 |
| og:image:alt | Summary This pull request introduces several additions to the JSON schema-validation utilities: Renamed the optional validator to optionalOrNull to clarify that schema fields may be optional and a... |
| og:site_name | GitHub |
| og:type | object |
| hostname | github.com |
| expected-hostname | github.com |
| None | 3d11bb817438277de2a940854450e83a7d32b6aeb5014e9e6b00a6423900251c |
| turbo-cache-control | no-preview |
| diff-view | unified |
| go-import | github.com/github/codeql-action git https://github.com/github/codeql-action.git |
| octolytics-dimension-user_id | 9919 |
| octolytics-dimension-user_login | github |
| octolytics-dimension-repository_id | 259445878 |
| octolytics-dimension-repository_nwo | github/codeql-action |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 259445878 |
| octolytics-dimension-repository_network_root_nwo | github/codeql-action |
| turbo-body-classes | logged-out env-production page-responsive full-width |
| disable-turbo | true |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | c03e7e569190bc89b638cdd4acb4b6c6b38a170a |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width