ruby.git/lib/error_highlight/base.rb, branch v3_4_9 The Ruby Programming Language [ruby/error_highlight] Fix error with prism when method given no arguments 2024-09-24T13:28:01+00:00 Luke Gruber luke.gru@gmail.com 2024-09-17T12:34:29+00:00 2a0ee408afeeae0f1a0d354ac36c400a361f6767 such as: p = Proc.new This now matches the RubyVM::AbstractSyntaxTree behavior, which is not to highlight anything. https://github.com/ruby/error_highlight/commit/d5c592a1ba 
such as:

  p = Proc.new

This now matches the RubyVM::AbstractSyntaxTree behavior, which is
not to highlight anything.

https://github.com/ruby/error_highlight/commit/d5c592a1ba
[ruby/error_highlight] Prism added node_id and Node#breadth_first_search in the 1.0 release. These methods are required for Prism to be able to find the method from the backtrace. 2024-09-24T06:33:31+00:00 Adam Hess hparker@github.com 2024-09-18T23:02:11+00:00 4b1e852d3ee79037e1b3963cc00c1407a7b3dda8 https://github.com/ruby/prism/blob/main/CHANGELOG.md#100---2024-08-28 In practice you will likely only end up in this situation if you previously had pre-1.0 prism installed and upgrade Ruby to a version with Prism as the default parser. https://github.com/ruby/error_highlight/commit/cb574daf62 
https://github.com/ruby/prism/blob/main/CHANGELOG.md#100---2024-08-28

In practice you will likely only end up in this situation if you previously had pre-1.0 prism installed and upgrade Ruby to a version with Prism as the default parser.

https://github.com/ruby/error_highlight/commit/cb574daf62
[PRISM] Use node ids for error highlight 2024-07-11T18:25:54+00:00 Kevin Newton kddnewton@gmail.com 2024-07-03T19:57:24+00:00 c1df15c3e69201ed01c1b902de8c9302740899eb 






[ruby/error_highlight] Trim trailing spaces in base.rb
2024-06-07T13:28:23+00:00

Kevin Newton
kddnewton@gmail.com

2024-06-07T13:26:55+00:00

51bb5dcd2e63d7902794d42147817733249d3dd9

https://github.com/ruby/error_highlight/commit/8ce3f6f145





https://github.com/ruby/error_highlight/commit/8ce3f6f145







[ruby/error_highlight] Support for the prism compiler
2024-06-07T13:15:14+00:00

Kevin Newton
kddnewton@gmail.com

2024-05-20T17:50:03+00:00

40ec860de761af3b7b8538452a55c2ef8b9bb93e

https://github.com/ruby/error_highlight/commit/69fbacfd49





https://github.com/ruby/error_highlight/commit/69fbacfd49







Add error for iseqs compiled by prism
2024-02-21T16:44:40+00:00

Kevin Newton
kddnewton@gmail.com

2024-02-14T15:58:20+00:00

82a4c3af1629298524024494fd065d51ff6ad5c6












[ruby/error_highlight] Identify which node in `Foo::Bar::Baz` causes a NameError
2023-01-13T08:25:09+00:00

Yusuke Endoh
mame@ruby-lang.org

2023-01-13T08:02:24+00:00

94d6d6d93fa40b5f8dcdda6aa0e4b300ee61085c

In Ruby 3.2 or later, a nested constant access like `Foo::Bar::Baz` is
compiled to one instruction by the optimization https://github.com/ruby/ruby/pull/6187

We try to spot which sub-node caues a NameError in question based on the
constant name. We will give up if the same constant name is accessed in
a nested access (`Foo::Foo`).

Fixes https://github.com/ruby/error_highlight/pull/31

https://github.com/ruby/error_highlight/commit/0a4db7da0a





In Ruby 3.2 or later, a nested constant access like `Foo::Bar::Baz` is
compiled to one instruction by the optimization https://github.com/ruby/ruby/pull/6187

We try to spot which sub-node caues a NameError in question based on the
constant name. We will give up if the same constant name is accessed in
a nested access (`Foo::Foo`).

Fixes https://github.com/ruby/error_highlight/pull/31

https://github.com/ruby/error_highlight/commit/0a4db7da0a







[ruby/error_highlight] Support nodes in `spot`
2022-10-31T04:58:38+00:00

eileencodes
eileencodes@gmail.com

2022-10-19T17:50:30+00:00

350d0aa023223f560d812ef61396a2c5359f09a6

Fixes a bug where `spot` was using the wrong local variable.

We want to use error highlight with code that has been eval'd,
specifically ERB templates. We can recover the compiled source code of
the ERB template but we need an API to pass the node into error
highlight's `spot`.

Required Ruby PR: https://github.com/ruby/ruby/pull/6593

https://github.com/ruby/error_highlight/commit/0b1b650a59

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>





Fixes a bug where `spot` was using the wrong local variable.

We want to use error highlight with code that has been eval'd,
specifically ERB templates. We can recover the compiled source code of
the ERB template but we need an API to pass the node into error
highlight's `spot`.

Required Ruby PR: https://github.com/ruby/ruby/pull/6593

https://github.com/ruby/error_highlight/commit/0b1b650a59

Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>







[ruby/error_highlight] Add a note about the current limitation of ErrorHighlight.spot
2022-08-12T05:04:41+00:00

Yusuke Endoh
mame@ruby-lang.org

2022-08-12T05:04:04+00:00

d9f1b8baa3a21b2a65af7fcab6a45c30b3f9efee

https://github.com/ruby/error_highlight/commit/489ce80a62





https://github.com/ruby/error_highlight/commit/489ce80a62







[ruby/error_highlight] Make backtrace_location keyword work
2022-08-10T12:19:10+00:00

Yusuke Endoh
mame@ruby-lang.org

2022-08-10T12:17:04+00:00

3a58009066049f9af09ea3171cecab88ba0d9f1c

We had to keep backtrace_location before opts is overwritten.

https://github.com/ruby/error_highlight/commit/2735e4681a





We had to keep backtrace_location before opts is overwritten.

https://github.com/ruby/error_highlight/commit/2735e4681a