You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to start differentiating between "logging" for which we'll use swift-log's interface, and "UI", which in the context of a CLI is the text that's part of the product experience and that's oriented towards communicating progress/actions to the developer that ran a command.
Noora components fall in the "UI" group, but I think it'd be beneficial to also log what the components do so that the logs can be used later on for debugging purposes.
The text was updated successfully, but these errors were encountered:
And then use it in implementing each component to leave a trace of what happened. For example, in the above case it can be:
logger.info("Prompted the user to select an option for the question '\(question)'")...
logger.info("Option '\(option)' selected for the question '\(question)'")
That way, consumers of this package can pass a Logger instance and provide a nice debugging experience to their users.
We need to start differentiating between "logging" for which we'll use swift-log's interface, and "UI", which in the context of a CLI is the text that's part of the product experience and that's oriented towards communicating progress/actions to the developer that ran a command.
Noora components fall in the "UI" group, but I think it'd be beneficial to also log what the components do so that the logs can be used later on for debugging purposes.
The text was updated successfully, but these errors were encountered: