This repository was archived by the owner on May 28, 2026. It is now read-only.
T421660: eslint enforce yml/no-empty-mapping-value#178
Merged
samwilson merged 1 commit intoApr 15, 2026
Conversation
okerekechinweotito
force-pushed
the
yml-no-empty-mapping-value
branch
from
499c2db to
eef2cd6
Compare
okerekechinweotito
force-pushed
the
yml-no-empty-mapping-value
branch
from
eef2cd6 to
1bdc97c
Compare
samwilson
approved these changes
Apr 15, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Related Phabricator Task - T421660
since empty value and
~appear to both representnullin yaml. I have added~as a placeholder to satisfy the ruleyml/no-empty-mapping-valuefrom .eslintrc.jsonyml/no-empty-mapping-valueerrorsnpm run testpasses