The percy debugger is a great tool, however, it's very misleading when referencing loading assets. It's important for us to keep the debugger on as we want to make sure Percy is not the reason why our CI failed or just check where it did fail.
For example:
[percy][DEBUG] Build resource: /filename.html
When our CI is essentially narrating what's going on, this makes it look like even though we're using the filesystem loader (as defined by [percy][DEBUG] Using filesystem_loader to discover assets.), assets are being loaded twice. We precompile assets as part of our config, so having Percy load it all a second time slows down our process/workflow a lot.
Feature request/suggestion: Change Build resource: /filename.html to Build resource found at /filename.html or something to indicate that Percy is not actually loading the files a second time, but just where the resource of the build is coming from.
The percy debugger is a great tool, however, it's very misleading when referencing loading assets. It's important for us to keep the debugger on as we want to make sure Percy is not the reason why our CI failed or just check where it did fail.
For example:
[percy][DEBUG] Build resource: /filename.htmlWhen our CI is essentially narrating what's going on, this makes it look like even though we're using the filesystem loader (as defined by
[percy][DEBUG] Using filesystem_loader to discover assets.), assets are being loaded twice. We precompile assets as part of our config, so having Percy load it all a second time slows down our process/workflow a lot.Feature request/suggestion: Change
Build resource: /filename.htmltoBuild resource found at /filename.htmlor something to indicate that Percy is not actually loading the files a second time, but just where the resource of the build is coming from.