Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Don't let users attempt to alias/merge arrays

未关闭
#349 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
ruby
领域
backend

调研方向

Start with the YAML.load example and inspect how Psych handles an alias used with the << merge key when the aliased value is an array. The change is done when this invalid array merge is rejected with an error instead of producing a hash containing the literal << key.

由索引模型根据 Issue 内容生成。

描述

I encountered the confusing behavior described below because I didn't realize that one couldn't merge arrays, only maps. Perhaps we should instead make the parser more strict and throw an error rather than producing the unexpected object structure?

The confusing behavior:

YAML.load("
# Bad! can't merge alias/arrays
foo: &foo  
  - a: 1
bar: 
  <<: *foo
")

=> {"foo"=>[{"a"=>1}], "bar"=>{"<<"=>[{"a"=>1}]}}

Note the appearance of the odd <<. I was expecting expected

   {"foo"=>[{"a"=>1}], "bar"=>[{"a"=>1}]}

As discussed here, my error is that the problem is that &foo is an attempted alias for an array. It would have been ideal if the parser had indicated my error instead.

In case relevant:

ENV['RBENV_VERSION']
=> "2.4"
YAML.libyaml_version
=> [0, 1, 4]

(Also, not entirely sure if this request belongs here or at https://github.com/yaml/libyaml , please feel free to redirect me!)

主要语言
Ruby
星标
597
派生
223
平均合并
14 分钟
30 天内合并 PR
1

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ruby/psych 的其他 Issue

查看 ruby/psych 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。