-
Notifications
You must be signed in to change notification settings - Fork 8
Add error message guidelines and how to build a PDF locally #45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…mation on building a PDF of the documentation locally on Windows
When writing error messages, follow the `Error Message Guidelines | ||
<https://docs.microsoft.com/en-us/windows/win32/debug/error-message-guidelines>`_ | ||
on the Microsoft website to ensure that your messages are well crafted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with these recommendations, is there potentially a more "Pythonic" style guide for error messages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akaszynski I've added two but you should probably check to see that they are good examples.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with suggestions.
Add Linux PDF build link Co-authored-by: Alex Kaszynski <[email protected]>
…s://github.com/pyansys/dev-guide into doc/add_error_message_and_building_pdf_locally # Conflicts: # doc/source/guidelines/doc_practices.rst
No description provided.