Repository navigation
Document use422ForNoDataStatusCode on the feature flags page - #106
Merged
Merged
Conversation
Follow-up to ERDDAP/erddap#606, which adds the flag. It shapes an HTTP response, so it sits with useHeadersForUrl and enableCors under Web Headers/Configuration.
ChrisJohnNOAA
approved these changes
Sep 28, 2026
ChrisJohnNOAA
left a comment
ChrisJohnNOAA
left a comment
Contributor
There was a problem hiding this comment.
Thanks for updating the documentation!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the
use422ForNoDataStatusCodeflag added in ERDDAP/erddap#606, as @ChrisJohnNOAA asked for on that PR.It shapes an HTTP response rather than dataset or metadata behavior, so it sits under Web Headers/Configuration next to
useHeadersForUrlandenableCorsrather than needing a page of its own. The entry follows the existing format: Lifecycle Stable, Current Default false, Long-term Goal "set as desired" (matchingenableCors, since this is an admin preference rather than a value to converge on).I put Added in 2.32.0 in the History row based on the version in the ERDDAP pom. Happy to change it if that PR is going to land in a different release, and this should probably only merge once it does.
One thing worth flagging separately:
npm run buildcurrently fails on a clean checkout of main, before any of my changes, while compilingi18n/ur/docusaurus-plugin-content-docs/current/server-admin/datasets.md:It looks like an Urdu full stop ended up appended to a URL in that translation. The same "Build site" step is failing in your own recent CI runs, so I do not think it is new, but it does mean CI on this PR will be red for reasons unrelated to it. I verified the failure is present with and without my change. Happy to open a separate issue or a fix for that translation file if it would help.