-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shakapacker v8: reintroduce https?
predicate
#486
Labels
Comments
Why can't you use just check Overall, I don't think it make sense to reintroduce this helper given how small it is and that the previous logic was deprecated upstream |
Thanks, I didn't check if it was available on legacy versions |
tagliala
added a commit
to tagliala/inline_svg
that referenced
this issue
May 25, 2024
Shakapacker is the official, actively maintained successor to Webpacker. Shakapacker v7 changed the spelling of `Webpacker` to `Shakapacker` in the entire project, but still provided backward compatibility for `Webpacker` spelling. v8 dropped the deprecated spelling This commit also: - Checks if `Shakapacker` is defined; if not, it falls back on `Webpacker`. - Uses the scope resolution operator to resolve at top-level scope - Checks `protocol` instead of `https?` because the former is available from Webpacker 3 and the latter is not available anymore in Shakapacker >= 8 Refs: - shakacode/shakapacker#414 - shakacode/shakapacker#429 - shakacode/shakapacker#486 Close jamesmartin#156
tagliala
added a commit
to tagliala/inline_svg
that referenced
this issue
Jun 24, 2024
Shakapacker is the official, actively maintained successor to Webpacker. Shakapacker v7 changed the spelling of `Webpacker` to `Shakapacker` in the entire project, but still provided backward compatibility for `Webpacker` spelling. v8 dropped the deprecated spelling This commit also: - Checks if `Shakapacker` is defined; if not, it falls back on `Webpacker`. - Uses the scope resolution operator to resolve at top-level scope - Checks `protocol` instead of `https?` because the former is available from Webpacker 3 and the latter is not available anymore in Shakapacker >= 8 Refs: - shakacode/shakapacker#414 - shakacode/shakapacker#429 - shakacode/shakapacker#486 Close jamesmartin#156
tagliala
added a commit
to tagliala/inline_svg
that referenced
this issue
Jul 27, 2024
Shakapacker is the official, actively maintained successor to Webpacker. Shakapacker v7 changed the spelling of `Webpacker` to `Shakapacker` in the entire project, but still provided backward compatibility for `Webpacker` spelling. v8 dropped the deprecated spelling This commit also: - Checks if `Shakapacker` is defined; if not, it falls back on `Webpacker`. - Uses the scope resolution operator to resolve at top-level scope - Checks `protocol` instead of `https?` because the former is available from Webpacker 3 and the latter is not available anymore in Shakapacker >= 8 Refs: - shakacode/shakapacker#414 - shakacode/shakapacker#429 - shakacode/shakapacker#486 Close jamesmartin#156
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Desired behavior:
Allow
Shakapacker::DevServer
respond tohttps?
predicate again, by checking ifprotcol == 'https'
. This will also allow a tiny refactor:shakapacker/lib/shakapacker/dev_server.rb
Line 53 in 295795e
If you are interested in reintroducing this predicate, I can submit a PR.
Use case: jamesmartin/inline_svg#158
Actual behavior:
DevServer does not respond to
https?
predicate anymoreSetup environment:
The text was updated successfully, but these errors were encountered: