rubyreferences / rubychanges Goto Github PK

I would send a PR, but I'm not sure exactly what is the relationship between 2.6.0.md and _src/2.6.0.md. I'm guessing the former is generated from the latter? In that case this might be a bug in Kramdown.

I think you want s/html/md/g

Apologies if this is the wrong place (perhaps I should open an issue in ruby/ruby for the NEWS.md instead?).

We've found an undocumented breaking change in Regexp.new that was put in place for https://bugs.ruby-lang.org/issues/18797

ruby/ruby@7e8fa06 changed the interface to issue a deprecation warning for the third parameter (in Ruby 3.2.0) and ruby/ruby@04cfb26 actually removed it (for Ruby 3.3.0)

See https://rubyreferences.github.io/rubychanges/3.1.html#threadbacktracelimit

I'd love to be able to consume this fantastic information you've created and provide an alternative visualization for it. For that, it would be far easier to consume a database that has discrete change entries with fields like: version, category, title, class, method, summary, overview, reason, discussion, documentation, example_code, notes, and so on.

The contents of many of these fields could/would be Markdown, and the full Markdown or HTML as present today could be generated from them.

Pros

1. People (like me) could consume the core data programmatically more easily
2. I think it would be more clear how to add new features in a consistent manner.
3. Would allow slicing the data different manners, e.g. creating a view that covers only the String class across all versions, or only the changes from 3.0 to 3.1.
4. (maybe not a pro?) The visual presentation would be forced to be consistent. For example, Notes: vs. Note:

Cons

1. A fair bit of scraping work (or manual conversion) would be need to convert the existing data
2. Removes the ability for custom presentation for a specific item, if desired. For example, if there was only one notes value per entry, or one example_code section, but you wanted two separate notes labeled separately.
3. Hand-editing Markdown-in-YAML does not have nice Markdown syntax highlighting.

https://github.com/rubyreferences/rubychanges/blob/master/_src/2.6.md?plain=1#L247

I tested it on
irb(main):117:0> RUBY_VERSION
=> "2.6.9"

I had to wrap additionally all compositions with &( function1 >> function2 )

Side Note: Faraday is weird and does not have method get, but it respond to it when send ...

Worked for me:

res = URLS.map(& (->(url) { Faraday.get url } >> :body.to_proc >> JSON.method(:parse) >> ->(data) { data.fetch('urls').map { |u| u['id'] } } ) )