Closed EatonZ closed 2 years ago
@SanderElias @jorgeucano I'm sorry, but this still doesn't appear to be fixed. Have you actually tested this feature? Re-run my sample app and you can still see a log file generated with Scully 1.0.6.
It didn't create one in my tests. But I do have a suspicion. Will look into this
@SanderElias Have you had time to take a look?
Yes, it isn't fixed yet, but i'm working on a pr that will solve this as a side-effect.
@SanderElias Which PR are you referring to? If it's already been merged let me know so I can check this and close if fixed.
I'm really unsure. If you check and find it id still open, please let me know
@SanderElias Checked today and the log file is still generated despite --logSeverity=none
.
Version 1.1.1
@EatonZ I just checked the code, and with the new setup of the way the background server is started, this should no longer create the file. (I checked 2.1.27). Can you confirm?
@SanderElias I attempted to build the sample project today, but it seems it's too old and throwing errors on npm install
.
I'll take your word for it if you noticed the issue no longer occurs. I do not have any active Angular projects right now.
🐞 Bug report
Description
The new
logSeverity
command line option added https://github.com/scullyio/scully/pull/988 unfortunately does not appear to be working. A log file still gets created.🔬 Minimal Reproduction
npm build
this application, thennpm scully
. Observe the createdscully.log
file. Notice how inpackage.json
, I added--logSeverity=none
toscully
.💻Your Environment
Angular Version:
Scully Version: