Open DRBragg opened 2 years ago
Haha @DRBragg top marks for the excellent gif usage to brighten up the bug report - I might mandate that in an issue template from now on 😂
Thanks for the through explanation/investigation - that definitely is a weird one though. I'll take a look to see if I can figure out what might be going on as soon as I get a chance.
Have a good weekend and I'll let you know as soon as I've got any ideas :-)
I thought if I couldn't write a good bug report I'd at least try to write a funny one.
Like I said def low priority!
This is a bit of an odd one so I apologize in advance. We're also on an older platform (Rails 5.1 and Ruby 2.5 😬 ) so I'm not sure how much of that plays into this. I try to open a PR when I find an older Ruby/Rails compatibility issue but this one has me a bit stumped.
Some background:
/components
config/initializers/lookbook.rb
) the looks like this:Previously, when navigating to
/components
we'd see the default "select a component" screen. After updating we get:Here's the console backtrace but it isn't very helpful
For S&G I added a catch all to our button component just to sanity check that it wasn't something goofy with my component or the preview but we still got a failure: If I navigate directly to a component preview (i.e.
components/inspect/button/primary
) It works fine and then the root (/components
) will suddenly start working. However, once I restart the server the root fails again.Other random stuff I've tried:
config.lookbook.experimental_features = [:pages]
from the config (why not)config.lookbook.page_paths = ["spec/components/docs"]
from the config (just in case)spec/components/docs
I have no explanation for this. I don't know why it fails without pages but works fine with them. I'm probably missing something silly but incase I'm not and this is an actual bug I wanted to open an issue. I'm happy to add any missing context or help debug further if I can.
FWIW We're planning on adding pages so this is low priority (for us at least).