This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/arrow-nanoarrow.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 8a4a45b update documentation for tag dev
8a4a45b is described below
commit 8a4a45bbbcb10fdae084ec46d37060dde038c975
Author: GitHub Actions <[email protected]>
AuthorDate: Thu Jul 20 16:28:50 2023 +0000
update documentation for tag dev
---
dev/_sources/getting-started_generated.rst.txt | 13 ++++++-------
dev/_sources/reference/c.rst.txt | 4 ++--
dev/getting-started.html | 13 +++++--------
dev/getting-started_generated.html | 13 +++++--------
dev/r/pkgdown.yml | 2 +-
5 files changed, 19 insertions(+), 26 deletions(-)
diff --git a/dev/_sources/getting-started_generated.rst.txt
b/dev/_sources/getting-started_generated.rst.txt
index 743b752..43180ce 100644
--- a/dev/_sources/getting-started_generated.rst.txt
+++ b/dev/_sources/getting-started_generated.rst.txt
@@ -485,13 +485,12 @@ Then, add the following to your ``CMakeLists.txt``:
include(GoogleTest)
gtest_discover_tests(linesplitter_test)
-| After you’re done, build the project again using the **CMake: Build**
- command from the command palette. If all goes well, choose **CMake:
- Refresh Tests** and then
-| **Test: Run All Tests** from the command pallete to run them! You
- should see some output indiciating that tests ran successfully, or you
- can use VSCode’s “Testing” panel to visually inspect which tests
- passed.
+After you’re done, build the project again using the **CMake: Build**
+command from the command palette. If all goes well, choose **CMake:
+Refresh Tests** and then **Test: Run All Tests** from the command
+pallete to run them! You should see some output indiciating that tests
+ran successfully, or you can use VSCode’s “Testing” panel to visually
+inspect which tests passed.
.. note::
If you're not using VSCode, you can accomplish the equivalent task in in a
terminal
diff --git a/dev/_sources/reference/c.rst.txt b/dev/_sources/reference/c.rst.txt
index 352d0e9..97d4d6e 100644
--- a/dev/_sources/reference/c.rst.txt
+++ b/dev/_sources/reference/c.rst.txt
@@ -55,12 +55,12 @@ Create, read, and modify schema metadata
.. doxygengroup:: nanoarrow-metadata
:members:
-Memory management
+Memory management
------------------
.. doxygengroup:: nanoarrow-malloc
:members:
-Error handling
+Error handling
------------------
.. doxygengroup:: nanoarrow-errors
:members:
diff --git a/dev/getting-started.html b/dev/getting-started.html
index 8e5d361..c85ef9c 100644
--- a/dev/getting-started.html
+++ b/dev/getting-started.html
@@ -765,15 +765,12 @@ the complexity of your project grows.</p>
<span class="nb">gtest_discover_tests</span><span class="p">(</span><span
class="s">linesplitter_test</span><span class="p">)</span>
</pre></div>
</div>
-<div class="line-block">
-<div class="line">After you’re done, build the project again using the
<strong>CMake: Build</strong>
+<p>After you’re done, build the project again using the <strong>CMake:
Build</strong>
command from the command palette. If all goes well, choose <strong>CMake:
-Refresh Tests</strong> and then</div>
-<div class="line"><strong>Test: Run All Tests</strong> from the command
pallete to run them! You
-should see some output indiciating that tests ran successfully, or you
-can use VSCode’s “Testing” panel to visually inspect which tests
-passed.</div>
-</div>
+Refresh Tests</strong> and then <strong>Test: Run All Tests</strong> from the
command
+pallete to run them! You should see some output indiciating that tests
+ran successfully, or you can use VSCode’s “Testing” panel to visually
+inspect which tests passed.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>If you’re not using VSCode, you can accomplish the equivalent task in in a
terminal
diff --git a/dev/getting-started_generated.html
b/dev/getting-started_generated.html
index 2d7f0d1..f53584c 100644
--- a/dev/getting-started_generated.html
+++ b/dev/getting-started_generated.html
@@ -763,15 +763,12 @@ the complexity of your project grows.</p>
<span class="nb">gtest_discover_tests</span><span class="p">(</span><span
class="s">linesplitter_test</span><span class="p">)</span>
</pre></div>
</div>
-<div class="line-block">
-<div class="line">After you’re done, build the project again using the
<strong>CMake: Build</strong>
+<p>After you’re done, build the project again using the <strong>CMake:
Build</strong>
command from the command palette. If all goes well, choose <strong>CMake:
-Refresh Tests</strong> and then</div>
-<div class="line"><strong>Test: Run All Tests</strong> from the command
pallete to run them! You
-should see some output indiciating that tests ran successfully, or you
-can use VSCode’s “Testing” panel to visually inspect which tests
-passed.</div>
-</div>
+Refresh Tests</strong> and then <strong>Test: Run All Tests</strong> from the
command
+pallete to run them! You should see some output indiciating that tests
+ran successfully, or you can use VSCode’s “Testing” panel to visually
+inspect which tests passed.</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>If you’re not using VSCode, you can accomplish the equivalent task in in a
terminal
diff --git a/dev/r/pkgdown.yml b/dev/r/pkgdown.yml
index fffbe38..0b78f14 100644
--- a/dev/r/pkgdown.yml
+++ b/dev/r/pkgdown.yml
@@ -2,5 +2,5 @@ pandoc: 2.9.2.1
pkgdown: 2.0.7
pkgdown_sha: ~
articles: {}
-last_built: 2023-07-19T14:03Z
+last_built: 2023-07-20T16:28Z
