Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use frontend:// as the default protocol for dependency annotation URLs
See original GitHub issue@HtmlImport, @JavaScript or @StyleSheet should in most cases be used together with frontend:// and this should thus be the default if no protocol is defined and the URL does not start with /.
The same logic should also be used by the corresponding Page.addXyz methods.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
HtmlImport (vaadin-all 8.16.1 API)
Relative URLs are mapped to APP/PUBLISHED/[url] which are by default served from the classpath relative to the class where the annotation is defined....
Read more >Web on Reactive Stack - Spring
By default, the starter uses Netty, but it is easy to switch to Tomcat, Jetty, or Undertow by changing your Maven or Gradle...
Read more >How to package your frontend in a Spring Boot App with ...
The first module is acme-example-api , which contains the backend API which, in turn, is just a simple @RestController annotated Spring MVC Controller....
Read more >Using Spring Boot for OAuth2 and JWT REST Protection - Toptal
This article is a guide on how to setup a server-side implementation of JSON Web Token (JWT) - OAuth2 authorization framework using Spring...
Read more >Configuring Ingress features | Google Kubernetes Engine (GKE)
To use the same BackendConfig for all ports of a Service or MultiClusterService, use the default key in the annotation. The Ingress controller...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Using
/bower_components/is a broken pattern that should be fixed regardless of WebJars.Without this issue fixed, they should be changed to
frontend://bower_components/. With this issue fixed, they can alternatively be changed tobower_components/. In either case, the code still needs to be fixed for WebJars to work.That’s what we’ve discussed about webJars implementation details: we have to get the request into our servlet in order to redirect it to corresponding webJar.
This means that urls like
/bower_components/...just won’t work with webjars andbower_components/...work already for them, no extra adjustments needed.That’s why they directly change a lot of related things.