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
Provide a simple means of extending error explanations and log messages which is optionally accessible within the messages themselves.
What would you like to see in the product?
Enable end users to click on links within KubeFox log and error messages which point to the XigXog website and which provide for deeper explanations, links to tutorials etc.
Give us an idea of the benefit to you and others should we fulfill the request
Error and log messages tend to be terse by design. Individual messages are frequently not immediately understandable by developers except for those who are already schooled in the art (of whatever product - including KubeFox). That puts developers in the position of hunting in the documentation for that information. By building links into the messages themselves, the developer is given a tremendous head start as they're pointed to the relevant part of the documentation. This will also generate information on what areas of the documentation are accessed the most, leading both to product improvements (ideally developers won't need to experience the issue in the first place) and documentation improvements.
Version
v0.5.x-beta
Code of Conduct
I agree to follow XigXog's Code of Conduct
The text was updated successfully, but these errors were encountered:
What are you trying to achieve?
Provide a simple means of extending error explanations and log messages which is optionally accessible within the messages themselves.
What would you like to see in the product?
Enable end users to click on links within KubeFox log and error messages which point to the XigXog website and which provide for deeper explanations, links to tutorials etc.
Give us an idea of the benefit to you and others should we fulfill the request
Error and log messages tend to be terse by design. Individual messages are frequently not immediately understandable by developers except for those who are already schooled in the art (of whatever product - including KubeFox). That puts developers in the position of hunting in the documentation for that information. By building links into the messages themselves, the developer is given a tremendous head start as they're pointed to the relevant part of the documentation. This will also generate information on what areas of the documentation are accessed the most, leading both to product improvements (ideally developers won't need to experience the issue in the first place) and documentation improvements.
Version
v0.5.x-beta
Code of Conduct
The text was updated successfully, but these errors were encountered: