Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add testing documentation #282

Merged
merged 4 commits into from
Sep 3, 2024
Merged

Add testing documentation #282

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dbe2a9c
[#134] Deprecation Docs: Fix list rendering
alanking Aug 29, 2024
dc9846b
[#226] Developer Docs: Adding and running tests
alanking Aug 29, 2024
48b9c79
[#222] Developer Docs: Using the testing environment
alanking Aug 29, 2024
91d87f5
[#205] Developer Docs: Testing server-only features
alanking Aug 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/developers/deprecation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ The following things need to be done whenever a feature is being declared as dep
4. If the feature is used by a client such as the iCommands and has user-facing help text, a note about the feature being deprecated should be included in the help text anywhere the feature is mentioned. If the feature being deprecated *is* an iCommand, a note about its deprecation can be included near the top of the help text.

The following rules should also be followed when deprecating an API:

- The API should NOT add a deprecation message to the RcComm or RsComm's rError object.
- The API should NOT emit a deprecation message to the log.

Expand Down
Loading
Loading