Update API specification #176
Merged
Conversation
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
airwoodix
force-pushed
the
update-api-spec
branch
from
016c9af to
12a7f06
Compare
wilfried-huss
approved these changes
Jun 26, 2024
fg-aqt
approved these changes
Jun 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Update the client to follow the latest AQT cloud portal public API specification.
There are no structural changes to the API models. The main changes are new constraints, e.g. on the circuit size.
Details and comments
The gate models' new description contain math code with illegal escape codes. The generated docstrings must therefore be declared as raw strings. This is done by applying the autofix for the ruff rule D301 (
escape-sequence-in-docstring). With some exceptions, the whole file is now linted and formatted.