You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug, including details regarding any error messages, version, and platform.
The document for Device Stream Interface shows the heading at Level 1, but it is not included in Section Navigation.
Is this intentional? If it's intentional, shouldn't the heading level for this content be Level 2? If it's not intentional, is it okay to adjust it to be positioned independently between The Arrow C Device data interface and Arrow Flight RPC?
Hmm, I think I agree that it would make sense for "Device Stream Interface" to use level 2 as it is technically a sub-level to the regular C Data Interface itself. I don't think it would be beneficial for them to be separate pages
### Rationale for this change
Noticed wrong section headings on the web doc and proposing a fix.
### Are these changes tested?
Yes. Built and verified the documentation locally.
<img width="1049" alt="image" src="https://github.com/apache/arrow/assets/6668548/793d6222-2bc5-4f55-ab67-5abe5283add4">
### Are there any user-facing changes?
No.
* Closes: #38599
Authored-by: Hyunseok Seo <hsseo0501@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
### Rationale for this change
Noticed wrong section headings on the web doc and proposing a fix.
### Are these changes tested?
Yes. Built and verified the documentation locally.
<img width="1049" alt="image" src="https://github.com/apache/arrow/assets/6668548/793d6222-2bc5-4f55-ab67-5abe5283add4">
### Are there any user-facing changes?
No.
* Closes: apache#38599
Authored-by: Hyunseok Seo <hsseo0501@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Describe the bug, including details regarding any error messages, version, and platform.
The document for
Device Stream Interface
shows the heading atLevel 1
, but it is not included inSection Navigation
.Is this intentional? If it's intentional, shouldn't the heading level for this content be
Level 2
? If it's not intentional, is it okay to adjust it to be positioned independently betweenThe Arrow C Device data interface
andArrow Flight RPC
?Component(s)
Documentation
The text was updated successfully, but these errors were encountered: