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
Polymer error message not formatted in Editor #20564
Comments
Set owner to @keertip. |
where did the message appear? |
As far as I can tell, this message is not produced by Editor. |
Looks like a debug message and not critical, so keeping at Medium. Removed the owner. |
I believe this is an editor bug. The polymer.js library now prints a formatted message, where %s is replaced by a number. The print normally comes formatted correctly in the chrome console, but if you launch the app from the editor, the editor console shows %s. Removed Area-Pkg, Pkg-Polymer labels. |
Set owner to @keertip. |
How do you reproduce this bug? Added NeedsInfo label. |
Set owner to @anders-sandholm. |
I think you can repro by just doing this: |
I did that, but I only see pub bootstrap stuff and then a bunch of GET requests. Maybe I missed it? --- 12:46:39 PM Auto running pub get on /Users/sethladd/dart/todomvc ... ---
--- 12:47:03 PM Starting pub serve : todomvc --- |
Just checked - there is a separate tab for the browser output (in this case it's labeled "index.html"), next to Tools Output |
Indeed! Thanks :) And yes, when I look inside the JS Console of Dartium, I see: flushing 10 elements But in editor's index.html panel/view, I see: flushing %s elements |
This is annoying, but has a workaround (open the Dartium console). Will close for now. Added NotPlanned label. |
Added this to the 1.7 milestone. |
Dart Editor version 1.6.0.dev_09_03 (DEV)
Dart SDK version 1.6.0-dev.9.3
The todomvc sample printed this unformatted message:
flushing %s elements (http://localhost:8080/packages/polymer/src/js/polymer/polymer.js:12)
Not clear if this is an Editor or Polymer bug. Assigning to Editor for now.
The text was updated successfully, but these errors were encountered: