-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add VDR API version usage with regards to DID methods to docs (#3400)
- Loading branch information
1 parent
7460f4a
commit 6a03263
Showing
3 changed files
with
32 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
.. _version-incompatibilities: | ||
|
||
Version Incompatibilities | ||
######################### | ||
|
||
V5/V6, DID methods and API versions | ||
*********************************** | ||
|
||
V6 introduced the support for multiple DID methods. To enable this, a new version of the VDR API has been added. | ||
There's also a config parameter that allows you to limit the DID methods in use. | ||
Not all combinations of API usage and DID methods are supported. | ||
There are basically two options. | ||
|
||
1. Keep using the VDR V1 API (for now) and set ``vdr.did_methods`` to ``["nuts"]``. | ||
2. Use the VDR V2 API and set ``vdr.did_methods`` to include other methods or leave blank for default setting. | ||
|
||
Do not use the VDR V1 and VDR V2 API at the same time. This will lead to unexpected behavior. | ||
Once you use the VDR V2 API, you cannot go back to the VDR V1 API. The VDR V1 API has also been marked as deprecated. | ||
|