9elements / aygabtu Goto Github PK

Use case is probably focus: true most of the time.

Maybe a scope method is the right way here, but that would require creating an artificial context when a scope method is used with an action, and not with a block.

NT

handle.rb:28 - @verbose
point_of_call:18 - @gem_root

https://github.com/thoughtbot/appraisal

Use case would be things like remaining.pend.

Totally doable, but what should it look like?

Due to the internal semantics of remaining, it is not possible to test remaining routes multiple times, i.e. in a desktop and mobile version.

remaining do
  visit
  visit_with(mobile_version: true)
end

When visiting the second (mobile) version, the route was already removed from aygabtu_matching_routes and thus no matching routes is found at runtime.

I had the problem that i run in an

Failure/Error: remaining.static_routes.visit
     RuntimeError:
       No matching route (action was: :visit, diagnostics: #<Aygabtu scope (remaining_at: CP 36, dynamic: false)>

error - took me a while to figure out that i need to wrap it in a

aygabtu_matching_routes(remaining).any?

my expectation was that it would be handeld by the gem so i have nothing to do with it...if there are no actions left to visit it should just skip the line, as expected when i call a .each on an empty array.

p.s.: what is CP?

An idea for another scope method, which matches routes which have no further (subtracting visiting_with params) url segments missing, something like:

requiring(:id).visiting_with(id: 5).visitable.visit