feat: document deprecation policy
This commit is contained in:
parent
a57be17dab
commit
b8f4e199f6
1 changed files with 7 additions and 0 deletions
|
@ -10,6 +10,13 @@ This is an unofficial client to various DHL APIs, more specific the ones that th
|
|||
|
||||
- app-driven parcel lockers (App-gesteuerte Packstation)
|
||||
|
||||
## Deprecation notice
|
||||
|
||||
It's recommended that consumers of this crate are always tracking the latest version. If the upstream API changes too much or a better API here is created, there are two ways to mark a function or struct deprecated:
|
||||
|
||||
- Soft deprecation/Crate API changes: The normal deprecation notice via `#[deprecated]` (see the [RFC#1270](https://github.com/rust-lang/rfcs/blob/master/text/1270-deprecation.md) or the [rust reference docs](https://doc.rust-lang.org/reference/attributes/diagnostics.html)).
|
||||
- (Fatal) Upstream API Changes: The soft deprecation marked with `deny(deprecated)`, you can try to override this, but functions with a `LibraryResult` will always return `LibraryError::Deprecated`. (NOTE: `LibrarayError::APIChange` is reserved for the case where the API-change is unknown. Please upgrade to a or wait for a newer crate version.)
|
||||
|
||||
## Examples
|
||||
|
||||
In the examples error-handling is ignored for simplicity. You don’t want to do that.
|
||||
|
|
Loading…
Reference in a new issue