-
Notifications
You must be signed in to change notification settings - Fork 81
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
Fix regressions in API generation script #67
Comments
Eric-Arellano
added a commit
that referenced
this issue
Oct 3, 2023
There were a couple of regressions in the API generation script since we last ran it in closed source. Those will be fixed in follow up PRs. See #67. This PR was created by simply copying and pasting the `api/` folders from closed source. They are generated files, so we don't have to worry about attribution.
Eric-Arellano
added a commit
that referenced
this issue
Oct 20, 2023
Fixes one of the issues in #67, that we weren't removing the permalink in headers with qiskit-ibm-runtime: ![screenshot_2023-10-20_at_11 17 25___am_720](https://github.com/Qiskit/documentation/assets/14852634/4fde70dc-e8c5-424f-9d34-c71cba68501a) This change is because of sphinx-doc/sphinx@7e9a206. Sphinx 7.2 changed the title from "Permalink" to "Link".
Eric-Arellano
added a commit
that referenced
this issue
Oct 20, 2023
In Qiskit docs, which use an older version of Sphinx, the module ID is set with HTML like this: ```html <span class="target" id="module-qiskit.circuit"> <span id="qiskit-circuit"></span> </span> ``` But in Runtime with Sphinx 7.2, it is set like this, without the `.target` class: ```html <span id="module-qiskit_ibm_runtime.options"></span> ``` So, we were failing to set metadata for modules, which caused those files to not have "front matter" (Markdown metadata) and to not show up in the TOC. See #67. Note that we still look at `section` to determine the module metadata, too. There continue to be some pages in IBM Provider that set their module metadata that way.
This was referenced Oct 20, 2023
The show stopper issues were fixed. I opened #224 for a small follow up. |
Eric-Arellano
added a commit
that referenced
this issue
Oct 24, 2023
frankharkins
pushed a commit
to frankharkins/documentation
that referenced
this issue
Jul 22, 2024
There were a couple of regressions in the API generation script since we last ran it in closed source. Those will be fixed in follow up PRs. See Qiskit#67. This PR was created by simply copying and pasting the `api/` folders from closed source. They are generated files, so we don't have to worry about attribution.
frankharkins
pushed a commit
to frankharkins/documentation
that referenced
this issue
Jul 22, 2024
Fixes one of the issues in Qiskit#67, that we weren't removing the permalink in headers with qiskit-ibm-runtime: ![screenshot_2023-10-20_at_11 17 25___am_720](https://github.com/Qiskit/documentation/assets/14852634/4fde70dc-e8c5-424f-9d34-c71cba68501a) This change is because of sphinx-doc/sphinx@7e9a206. Sphinx 7.2 changed the title from "Permalink" to "Link".
frankharkins
pushed a commit
to frankharkins/documentation
that referenced
this issue
Jul 22, 2024
In Qiskit docs, which use an older version of Sphinx, the module ID is set with HTML like this: ```html <span class="target" id="module-qiskit.circuit"> <span id="qiskit-circuit"></span> </span> ``` But in Runtime with Sphinx 7.2, it is set like this, without the `.target` class: ```html <span id="module-qiskit_ibm_runtime.options"></span> ``` So, we were failing to set metadata for modules, which caused those files to not have "front matter" (Markdown metadata) and to not show up in the TOC. See Qiskit#67. Note that we still look at `section` to determine the module metadata, too. There continue to be some pages in IBM Provider that set their module metadata that way.
frankharkins
pushed a commit
to frankharkins/documentation
that referenced
this issue
Jul 22, 2024
Now that we fixed Qiskit#67, we can regenerate the API docs. The issues were due to changes with modern Sphinx 7.2. There was one regression I noticed, but it's not enough of a show-stopper to block this PR: Qiskit#224.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Detected in #68.
in qiskit
alt textdocumentation/docs/api/qiskit-ibm-provider/qiskit_ibm_provider.IBMBackend.md
Line 17 in ab783b4
Note the"(in Qiskit v0.44)"
text.I'm not sure what is expected? This is how https://qiskit.org/ecosystem/ibm-provider/stubs/qiskit_ibm_provider.IBMBackend.html#qiskit_ibm_provider.IBMBackend renders:This is not a bug. It's intentional and sets the HTML anchor
title
.IBM Runtime no TOC children (fixed in #221)
documentation/docs/api/qiskit-ibm-runtime/_toc.json
Lines 4 to 9 in ab783b4
IBM runtime missing header (fixed in #221)
documentation/docs/api/qiskit-ibm-runtime/options.md
Line 1 in ab783b4
Was originally:
IBM runtime bad headers (fixed in #212)
Shouldn't have the
[¶]
character.documentation/docs/api/qiskit-ibm-runtime/ibm-runtime.md
Line 1 in ab783b4
The text was updated successfully, but these errors were encountered: