I'm considering dropping it especially for single action controllers.
"StoreContentAnalysisFeedback" seems better than "StoreContentAnalysisFeedbackController", especially when viewing it in the routes file.
@laravelphp I've bumped the open PR and sent an email to the maintainer with no response. I would like to keep developing the package and release it but I'm not sure if that's ethical. What do you think I should do?
I'm curious if anyone knows the protocol for this situation: I've used a particular @laravelphp package for a handful of projects in the past. Initially the maintainer accepted PRs but has been radio-silent for many months now.
Has anyone experienced similar and found a solution? This is driving me nuts, especially since the @laravelphp suite of sites (https://t.co/Hmyiw3D3nQ, https://t.co/UIbaguGvAe, forge) won't load!
I have a growing list of sites that will not load in Chrome (or Brave). They load fine on Safari or Firefox on the same device. Other machines on the same network can access them on all browsers. I've disabled all extensions, tried new profiles, deleted/reinstalled, with no luck.
Since then we've launched a handful of different versions of https://t.co/0W1yEgbvQr.
The newest iteration deployed today was a massive team effort. Thanks to @jasmineatracey, @ajp, @metadaptive, and others for the outstanding work.