Code Climate has analyzed commit fc70f6d and detected 0 issues on this pull request.

View more on Code Climate.

Hi @Eddayy, thanks for submitting this. Could you please specify which component failed to eject and provide the Rails/Ruby version used?

Hi @Eddayy, thanks for submitting this. Could you please specify which component failed to eject and provide the Rails/Ruby version used?

Sorry i didn't include it, here are the details
Ruby 3.3.5
Rails 7.1.2
Command used bin/rails g avo:eject --component Avo::Views::ResourceIndexComponent

Thanks for sharing @Eddayy

It's not failing on my side, any tip on how to reproduce it?

╭─bob@machine ~/Projects/gems/avo/spec/dummy ‹main●› 
╰─$ ruby -v & rails -v & bin/rails g avo:eject --component Avo::Views::ResourceIndexComponent
[1] 17013
[2] 17014
ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [x86_64-linux]
[1]  - 17013 done       ruby -v
Rails 7.1.2
[2]  + 17014 done       rails -v
warning: parser/current is loading parser/ruby33, which recognizes 3.3.6-compliant syntax, but you are running 3.3.5.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Running via Spring preloader in process 17107
Avo community 3.15.7
By ejecting the 'Avo::Views::ResourceIndexComponent' you'll take on the responsibility for maintain it.
Are you sure you want to eject the 'Avo::Views::ResourceIndexComponent'? [y/N] y
      create  app/components/avo/views/resource_index_component.rb
      create  app/components/avo/views/resource_index_component.html.erb

@Paul-Bob, turn out I'm having the issue because when installing avo on a new rails app, it install a newer view_component gem with version 3.21.0 instead of 3.20.0 used in the dummy app, 3.21.0 removes source_location and uses identifier instead, i'll updated it accordingly, it works for avo using both before and after the change

Related PR
ViewComponent/view_component#2153