It would be nice to have multiple levels of logging in roku-deploy to help debug issues when they arise. Here are the following tasks necessary to complete this:
add new option to RokuDeployOptions called logLevel with the following signature:
logLevel: 'error' | 'warn' | 'log' | 'info' | 'debug' | 'trace'
logLevel should be supported in the following scenarios:
passed in as --log-level from the command line (see this section in brighterscript for how to parse from the command line).
passed in the options: RokuDeployOptions anywhere in roku-deploy
loded from roku-deploy.json
loaded from bsconfig.json
use @rokucommunity/logger package in this project, and make it an instance variable on the RokuDeploy class so it can be mocked or swapped out during tests or other situations.
convert any current console.* calls in roku-deploy to use this.logger.*.
TwitchBronBron
commented
1 month ago
It would be nice to have multiple levels of logging in
roku-deployto help debug issues when they arise. Here are the following tasks necessary to complete this:add new option to
RokuDeployOptionscalledlogLevelwith the following signature:logLevel: 'error' | 'warn' | 'log' | 'info' | 'debug' | 'trace'logLevelshould be supported in the following scenarios:--log-levelfrom the command line (see this section in brighterscript for how to parse from the command line).options: RokuDeployOptionsanywhere inroku-deployroku-deploy.jsonbsconfig.jsonuse @rokucommunity/logger package in this project, and make it an instance variable on the
RokuDeployclass so it can be mocked or swapped out during tests or other situations.convert any current
console.*calls inroku-deployto usethis.logger.*.add additional logging calls as needed