You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With recent Flow versions a check for multiple dependency loading strategies was introduced:
07:13:35 qtp1018959698-137 2018-03-09 09:13:35 WARN [c.v.f.c.i.DependencyList] - Dependency with url frontend://components/../bower_components/polymer/lib/elements/custom-style.html was imported with two different loading strategies: EAGER and LAZY. The loading strategy is changed to EAGER to avoid conflicts. This may impact performance.
07:13:35 qtp1018959698-137 2018-03-09 09:13:35 ERROR [c.v.f.s.DefaultErrorHandler] -
07:13:35 java.lang.IllegalStateException: Dependency with url frontend://components/../bower_components/polymer/lib/elements/custom-style.html is loaded both with LAZY and EAGER modes
07:13:35 at com.vaadin.flow.component.internal.DependencyList.checkDuplicateDependency(DependencyList.java:94)
07:13:35 at com.vaadin.flow.component.internal.DependencyList.lambda$add$0(DependencyList.java:76)
This information is good, but please, just log a warning. It isn't that severe that an exception should be thrown that will stop loading the whole view.
The text was updated successfully, but these errors were encountered:
It makes no sense to crash the App when developer accidentally adds the
same resource with two different load modes.
For now when duplicates are added during the same roundtrip, the more
eager load mode is used.
Fixes#3677
It makes no sense to crash the App when developer accidentally adds the
same resource with two different load modes.
For now when duplicates are added during the same roundtrip, the more
eager load mode is used.
Fixes#3677
It makes no sense to crash the App when developer accidentally adds the
same resource with two different load modes.
For now when duplicates are added during the same roundtrip, the more
eager load mode is used.
Fixes#3677
It makes no sense to crash the App when developer accidentally adds the
same resource with two different load modes.
For now when duplicates are added during the same roundtrip, the more
eager load mode is used.
Fixes#3677
* Do not crash app for using different load modes
It makes no sense to crash the App when developer accidentally adds the
same resource with two different load modes.
For now when duplicates are added during the same roundtrip, the more
eager load mode is used.
Fixes#3677
With recent Flow versions a check for multiple dependency loading strategies was introduced:
This information is good, but please, just log a warning. It isn't that severe that an exception should be thrown that will stop loading the whole view.
The text was updated successfully, but these errors were encountered: