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
{{ message }}
This repository has been archived by the owner on Dec 20, 2023. It is now read-only.
When writing code that is hardware-platform independent (as is the case for some shared code in OpenWeave example applications), it would be great to have the ability to rely on a logging facility that is also platform-independent.
The OpenWeave logging mechanism is perfect for that. However, it would be great to have a new module, for example "Application", that would clarify that the logging message was triggered within application code.
The text was updated successfully, but these errors were encountered:
When writing code that is hardware-platform independent (as is the case for some shared code in OpenWeave example applications), it would be great to have the ability to rely on a logging facility that is also platform-independent.
The OpenWeave logging mechanism is perfect for that. However, it would be great to have a new module, for example "Application", that would clarify that the logging message was triggered within application code.
The text was updated successfully, but these errors were encountered: