0-13-development: Ran Prettier

Author: dobrienCP

README.md

@@ -376,27 +376,33 @@ Links to headings must not include an extra slash between the name of the page a
     <img src="/static/img/readme_images/readme_solidworks_image_4.png" width="800"/>
 
 ## Mermaid Diagrams
+
 Mermaid is a JavaScript based diagram generator that uses Markdown for descriptions and is available to docusaurus through a [plug-in](https://docusaurus.io/docs/next/markdown-features/diagrams).
 
 To get started with Mermaid diagrams, use their [live tool](https://mermaid.live/edit). The live viewing tool is useful to explore the various diagrams using their readily available templates.
->> Currently, we are on version 2.4.3 of the Mermaid plug-in. Therefore, not all of the templates in the live version are available.
+
+> > Currently, we are on version 2.4.3 of the Mermaid plug-in. Therefore, not all of the templates in the live version are available.
 
 Although Mermaid is more complicated to use than other tools, it is easy to version and outputs HTML objects; the resulting diagrams can include links and the text within it is searchable. Additionally, HTML tags can be included within the diagrams for further customization. Refer to the [Mermaid Documentation](https://mermaid.js.org/intro/getting-started.html) for more details on the diagram descriptions.
 
 ### Themes
+
 In the [Docusaurus configuration file](./docusaurus.config.js), we have defined the site-wide themes for the Mermaid diagrams. Mermaid offers a choice of five different themes to choose from. There is a way to call the `mermaidAPI` to set a customized site-wide theme, however, this has not yet been implemented.
 
 See their [theming documentation](https://mermaid.js.org/config/theming.html) for more information.
 
 ### Creating a Diagram
+
 In Docusaurus, we can use a [dyanmic Mermaid component](https://docusaurus.io/docs/next/markdown-features/diagrams#component) to define and load diagrams.
 
 First, we import the dynamic component.
+
 ```
 import Mermaid from '@theme/Mermaid';
 ```
 
 Then, we instantiate the component with the graph passed in as an argument.
+
 ```
 <Mermaid
   value={`
@@ -410,9 +416,11 @@ Then, we instantiate the component with the graph passed in as an argument.
 ```
 
 ### Configuring the Diagram
+
 Diagrams can be modified indepent from the site-wide theme and configuration using [directives](https://mermaid.js.org/config/directives.html). Essentially, these directives are used to pass in an initialization configuration to the local diagram that overrides the existing global configuration.
 
 For example, we can modify the way the arrow connecting two nodes is generated. Instead of the default, we can set the `curve` parameter to `step` to have the generated arrow move in steps rather than a smooth curve.
+
 ```
 <Mermaid
   value={`
@@ -434,10 +442,10 @@ For example, we can modify the way the arrow connecting two nodes is generated.
 
 Notice that when defining a directive within the dynamic component, we must end every line with a backslash `\`. Make sure to not have any trailing commas, `,`, at the end of a list or dictionary.
 
-See the [flowchart configuration](
-https://mermaid.js.org/config/schema-docs/config-defs-flowchart-diagram-config.html) to see all the settings specific to flowcharts that can be modified with directives.
+See the [flowchart configuration](https://mermaid.js.org/config/schema-docs/config-defs-flowchart-diagram-config.html) to see all the settings specific to flowcharts that can be modified with directives.
 
 You may notice that there is no way to set the font size through the diagram's configuration. Instead that must be done by modifying the theme variables.
+
 ```
 <Mermaid
   value={`
@@ -459,10 +467,11 @@ You may notice that there is no way to set the font size through the diagram's c
   `}
 />
 ```
-See the (Mermaid configuration)[https://mermaid.js.org/config/schema-docs/config.html] documentation page for an exhaustive list of parameters.
 
+See the (Mermaid configuration)[https://mermaid.js.org/config/schema-docs/config.html] documentation page for an exhaustive list of parameters.
 
 Even though the font size has been modified, the rendered diagram's font may not appear to change size. Instead, the text size will remain a relatively similar size while the boxes and arrows appear smaller. Therefore, the sure-fire method to set a font size is to use HTML `<font size=10></font>` tags to wrap the text within a node.
+
 ```
 <Mermaid
   value={`

docs_outdoornav_user_manual/api/api_endpoints/autonomy_api.mdx

@@ -16,7 +16,6 @@ The OutdoorNav software publishes to the topics in this section either
 all the time or while an autonomous navigation missions is running. They
 can be used to monitor the behaviour of OutdoorNav.
 
-
 #### /assisted_teleop/cmd_vel
 
   **Message Type:** geometry_msgs/Twist
@@ -88,14 +87,14 @@ including autonomy state and mode.
 
   **Message Type:** [clearpath_dock_msgs/DockProperties](definitions.mdx#msg-dock-properties)
 
-  **Description:**  A list of docks, in which each dock includes information related to
+  **Description:** A list of docks, in which each dock includes information related to
 the location, id, etc...
 
 #### /dock/state
 
   **Message Type:** [clearpath_dock_msgs/DockState](definitions.mdx#msg-dock-state)
 
-  **Description:**  The current state of the docking process.
+  **Description:** The current state of the docking process.
 
 #### /localization/odom
 
@@ -169,7 +168,7 @@ the robot along the reference path.
   **Message Type:** [clearpath_navigation_msgs/Metrics](definitions.mdx#msg-metrics)
 
   **Description:** This topic provides metric information regarding the lifetime of
-the navigation. This includes the total distance travelled, duration run, as well as mission 
+the navigation. This includes the total distance travelled, duration run, as well as mission
 information such as how many missions have been sent, how many have been completed and the number
 of replanning maneuvers, recoveries and number of tasks executed.
 
@@ -242,8 +241,8 @@ direction).
 
   **Message Type:** [clearpath_logger_msgs/DeleteLog](definitions.mdx#srv-log-deletelog)
 
-  **Description:** Deletes a log as specified by the UUID provided. If the purge flag is set the log will be removed from 
-the internal records entirely. If not, then the record will be marked as deleted and the meta data preserved, though log data will still 
+  **Description:** Deletes a log as specified by the UUID provided. If the purge flag is set the log will be removed from
+the internal records entirely. If not, then the record will be marked as deleted and the meta data preserved, though log data will still
 be deleted.
 
 #### /onav_log/download_kmz
@@ -348,7 +347,7 @@ message for 1 second).
 
   **Description:** Result topic from the undock action.
 
-------------------------------------------------------------------------
+---
 
 ### Topics Subscribed to by Autonomy
 
@@ -405,7 +404,7 @@ initialized by a previously sent goal.
   **Description:** This topic is used to send a goal to the undocking process.
 The goal is empty since we always consider undocking to be a local undocking process.
 
-------------------------------------------------------------------------
+---
 
 ### Services Exported by Autonomy
 
@@ -461,7 +460,7 @@ the location of an existing dock (where the `uuid` field is required).
 
   **Service Type:** [clearpath_dock_msgs/srv/SetDockLocationByName](definitions.mdx#srv-set-dock-location-by-name)
 
-  **Description:** Can be used to update the location of an existing dock. Requires the semantic name 
+  **Description:** Can be used to update the location of an existing dock. Requires the semantic name
 of the dock to be input into the `name` field.
 
 #### /localization/set_datum
@@ -497,9 +496,9 @@ should be used with caution.
 1.  This feature does not take effect immediately when the service is
     called, but only takes effect at the next Goal.
 
-2. Disabling collision avoidance also disables the continuous planner, in such a case where the
-   continuous planner is enabled. When re-enabling the collision avoidance,
-   the continuous planner must also be re-enabled using the following API service.
+2.  Disabling collision avoidance also disables the continuous planner, in such a case where the
+    continuous planner is enabled. When re-enabling the collision avoidance,
+    the continuous planner must also be re-enabled using the following API service.
 
 :::
 
@@ -570,7 +569,7 @@ True, delay compensation is ENABLED and the controller will compensate
 for low-level mechanical delays. If False, delay compensation is
 DISABLED and the normal behaviour is expected.
 
-------------------------------------------------------------------------
+---
 
 ### Actions Exported by Autonomy
 
@@ -631,4 +630,4 @@ goal tolerances, goal heading, an optional start_waypoint_uuid, and a from_start
   **Action Type:** [clearpath_dock_msgs/action/Dock](definitions.mdx#action-undock)
 
   **Description:** Undock the robot to the charging dock, if the docking
-package has been included.
+package has been included.

docs_outdoornav_user_manual/api/api_endpoints/definitions.mdx

@@ -841,26 +841,26 @@ bool[] camera_watchdog_triggered
 
 #### Standard ROS Messages {#std-ros-msgs}
 
--   [actionlib_msgs/GoalID](http://docs.ros.org/en/noetic/api/actionlib_msgs/html/msg/GoalID.html)
--   [diagnostic_msgs/DiagnosticArray](http://docs.ros.org/en/noetic/api/diagnostic_msgs/html/msg/DiagnosticArray.html)
--   [geometry_msgs/PolygonStamped](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/PolygonStamped.html)
--   [geometry_msgs/Polygon](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/Polygon.html)
--   [geometry_msgs/PoseArray](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/PoseArray.html)
--   [geometry_msgs/Twist](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/Twist.html)
--   [nav_msgs/OccupancyGrid](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/OccupancyGrid.html)
--   [nav_msgs/Odometry](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Odometry.html)
--   [nav_msgs/Path](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Path.html)
--   [sensor_msgs/Imu](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/Imu.html)
--   [sensor_msgs/LaserScan](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/LaserScan.html)
--   [sensor_msgs/NavSatFix](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/NavSatFix.html)
--   [sensor_msgs/PointCloud2](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/PointCloud2.html)
--   [std_msgs/Bool](http://docs.ros.org/en/noetic/api/std_msgs/html/msg/Bool.html)
--   [std_msgs/Empty](http://docs.ros.org/en/noetic/api/std_msgs/html/msg/Empty.html)
--   [std_msgs/String](http://docs.ros.org/en/noetic/api/std_msgs/html/msg/String.html)
--   [tf2_msgs/TFMessage](http://docs.ros.org/en/noetic/api/tf2_msgs/html/msg/TFMessage.html)
--   [wireless_msgs/Connection](http://docs.ros.org/en/noetic/api/wireless_msgs/html/msg/Connection.html)
-
-------------------------------------------------------------------------
+- [actionlib_msgs/GoalID](http://docs.ros.org/en/noetic/api/actionlib_msgs/html/msg/GoalID.html)
+- [diagnostic_msgs/DiagnosticArray](http://docs.ros.org/en/noetic/api/diagnostic_msgs/html/msg/DiagnosticArray.html)
+- [geometry_msgs/PolygonStamped](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/PolygonStamped.html)
+- [geometry_msgs/Polygon](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/Polygon.html)
+- [geometry_msgs/PoseArray](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/PoseArray.html)
+- [geometry_msgs/Twist](http://docs.ros.org/en/noetic/api/geometry_msgs/html/msg/Twist.html)
+- [nav_msgs/OccupancyGrid](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/OccupancyGrid.html)
+- [nav_msgs/Odometry](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Odometry.html)
+- [nav_msgs/Path](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Path.html)
+- [sensor_msgs/Imu](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/Imu.html)
+- [sensor_msgs/LaserScan](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/LaserScan.html)
+- [sensor_msgs/NavSatFix](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/NavSatFix.html)
+- [sensor_msgs/PointCloud2](http://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/PointCloud2.html)
+- [std_msgs/Bool](http://docs.ros.org/en/noetic/api/std_msgs/html/msg/Bool.html)
+- [std_msgs/Empty](http://docs.ros.org/en/noetic/api/std_msgs/html/msg/Empty.html)
+- [std_msgs/String](http://docs.ros.org/en/noetic/api/std_msgs/html/msg/String.html)
+- [tf2_msgs/TFMessage](http://docs.ros.org/en/noetic/api/tf2_msgs/html/msg/TFMessage.html)
+- [wireless_msgs/Connection](http://docs.ros.org/en/noetic/api/wireless_msgs/html/msg/Connection.html)
+
+---
 
 ### Service Definitions
 
@@ -1192,6 +1192,7 @@ string[] tags
 ```
 
 #### clearpath_mission_manager_msgs/srv/CloneMission.srv {#storage-clonemission}
+
 ```
 # The UUID of the mission to clone
 string uuid
@@ -2054,10 +2055,10 @@ string message
 
 #### Standard ROS Services
 
--   [std_srvs/Empty](http://docs.ros.org/en/noetic/api/std_srvs/html/srv/Empty.html)
--   [std_srvs/SetBool](http://docs.ros.org/en/noetic/api/std_srvs/html/srv/SetBool.html)
+- [std_srvs/Empty](http://docs.ros.org/en/noetic/api/std_srvs/html/srv/Empty.html)
+- [std_srvs/SetBool](http://docs.ros.org/en/noetic/api/std_srvs/html/srv/SetBool.html)
 
-------------------------------------------------------------------------
+---
 
 ### Action Definitions
 
@@ -2170,7 +2171,6 @@ bool success
 float32 percent_complete
 ```
 
-
 #### clearpath_mission_scheduler_msgs/action/RunScheduleByUuid.action {#scheduler-runschedulebyuuid}
 
 ```
@@ -2337,4 +2337,4 @@ string message
 # feedback
 string message
 clearpath_navigation_msgs/NetworkMissionSegment network_plan
-```
+```