Análises de ChromeLogger
ChromeLogger por BurningMoth
24 análises
- Avaliado em 5 de 5por Marc, há 2 meses
- Avaliado em 5 de 5por AmericanIntelligenceMachines, há 5 meses
- Avaliado em 5 de 5por Usuário 17447093 do Firefox, há 3 anos
- Avaliado em 5 de 5por Usuário 16987925 do Firefox, há 4 anos
- Avaliado em 5 de 5por Usuário 15064500 do Firefox, há 6 anos
- Avaliado em 5 de 5por Usuário 14666722 do Firefox, há 6 anos
- Avaliado em 5 de 5por Usuário 13079274 do Firefox, há 7 anos
- Avaliado em 5 de 5por Usuário 14035565 do Firefox, há 7 anos
- Avaliado em 5 de 5por Joe Rooster, há 7 anosWorks as expected and better than other add-ons that (try to) put out messages from ChromePHP. Thank you :-)
- Avaliado em 5 de 5por Usuário 13483795 do Firefox, há 8 anosOk so the problems I reported earlier are fixed and logging is working as expected now. Thanks for a great bit of digital kit?
- Avaliado em 5 de 5por Patrick Brosset, há 8 anosWorks for me now. It was updated last week and it fixes the issue people have been talking about in the comments!
Thanks! - Avaliado em 5 de 5por Usuário 13328225 do Firefox, há 8 anosSince version 1.1.1 it works as it should. Thanks!
- Updated Review:
Issue's been resolved and logs my messages like a champ.
Previous Review:
Produces error: TypeError: window.console[method] is undefined
The reason appears to be that it assumes the console method will be sent in the response. This will be the case for the all logging types _except_ "log". According to the Chrome Logger technical specifications at https://craig.is/writing/chrome-logger/techspecs, if you want to log, you should send an empty string (to save on size). Therefore the add-on ought to use "log" if "method" is empty. I believe the following would be sufficient to fix it:
console[method || 'log']
I couldn't find a repository to log this issue at or submit a pull request, so I had to use the review section.