support passing through options to `YAML.safe_load`
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 37
- Forks
- 13
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
With the changes in https://github.com/ruby/yaml/pull/41, this has broken our ability to store non-permitted classes. It would be great to be able to pass-through options to ::safe_load or at least choose to use ::unsafe_load. Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the changes in ruby/yaml pull request 41 and the current use of YAML.safe_load. Determine how options could be passed through or how unsafe_load could be selected. Done means the existing ability to load non-permitted classes is restored through a defined API, with the behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100