Skip to content

fix(yaml): fix !!pairs parsing #5192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 29, 2024
Merged

Conversation

kt3k
Copy link
Member

@kt3k kt3k commented Jun 28, 2024

This PR fixes the handling of empty pairs, and also adds the test cases for parsing various !!pairs patterns.

@github-actions github-actions bot added the yaml label Jun 28, 2024
@@ -9,6 +9,8 @@ import type { Any } from "../_utils.ts";
const _toString = Object.prototype.toString;

function resolveYamlPairs(data: Any[][]): boolean {
if (data === null) return true;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link

codecov bot commented Jun 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.44%. Comparing base (965833b) to head (79a9616).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5192      +/-   ##
==========================================
+ Coverage   94.38%   94.44%   +0.05%     
==========================================
  Files         467      467              
  Lines       37819    37820       +1     
  Branches     5485     5491       +6     
==========================================
+ Hits        35696    35719      +23     
+ Misses       2085     2062      -23     
- Partials       38       39       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@kt3k kt3k merged commit 9c543c9 into denoland:main Jun 29, 2024
15 checks passed
@kt3k kt3k deleted the fix-yaml-pairs-handling branch June 29, 2024 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants