PyPI - nautobot - Versions diffs - 2.4.0__py3-none-any.whl → 2.4.0b1__py3-none-any.whl - Mend - Supply Chain Defender

nautobot 2.4.0py3-none-any.whl → 2.4.0b1py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.

This version of nautobot might be problematic. Click here for more details.

Files changed (592) hide show

nautobot/project-static/docs/code-reference/nautobot/apps/api.html CHANGED Viewed

@@ -18,7 +18,7 @@
       <link rel="icon" href="../../../assets/favicon.ico">
-      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.49">
+      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.46">
@@ -2112,27 +2112,6 @@
-    <li class="md-nav__item">
-      <a href="../../../user-guide/feature-guides/wireless-networks-and-controllers.html" class="md-nav__link">
-  <span class="md-ellipsis">
-    Wireless Networks and Controllers
-  </span>
-      </a>
-    </li>
           </ul>
         </nav>
@@ -5152,27 +5131,6 @@
-    <li class="md-nav__item">
-      <a href="../../../user-guide/platform-functionality/jobs/kubernetes-job-support.html" class="md-nav__link">
-  <span class="md-ellipsis">
-    Kubernetes Job Support
-  </span>
-      </a>
-    </li>
     <li class="md-nav__item">
       <a href="../../../user-guide/platform-functionality/jobs/jobbutton.html" class="md-nav__link">
@@ -7194,15 +7152,6 @@
     </span>
   </a>
-</li>
-          <li class="md-nav__item">
-  <a href="#nautobot.apps.api.ModelViewSetMixin.get_queryset" class="md-nav__link">
-    <span class="md-ellipsis">
-      get_queryset
-    </span>
-  </a>
 </li>
           <li class="md-nav__item">
@@ -8998,11 +8947,11 @@
     <li class="md-nav__item">
-      <a href="../../../development/core/minikube-dev-environment-for-k8s-jobs.html" class="md-nav__link">
+      <a href="../../../development/core/local-k8s.html" class="md-nav__link">
   <span class="md-ellipsis">
-    Minikube Dev Environment for K8s Jobs
+    Local Kubernetes Cluster
   </span>
@@ -10118,15 +10067,6 @@
     </span>
   </a>
-</li>
-          <li class="md-nav__item">
-  <a href="#nautobot.apps.api.ModelViewSetMixin.get_queryset" class="md-nav__link">
-    <span class="md-ellipsis">
-      get_queryset
-    </span>
-  </a>
 </li>
           <li class="md-nav__item">
@@ -10800,12 +10740,7 @@
     <div class="doc doc-contents first">
-        <p>Helpers for an app to implement a REST API.</p>
+      <p>Helpers for an app to implement a REST API.</p>
@@ -10831,15 +10766,10 @@
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="nautobot.core.api.views.NautobotAPIVersionMixin">NautobotAPIVersionMixin</span></code>, <code><span title="rest_framework.routers.APIRootView">APIRootView</span></code></p>
-        <p>Extends DRF's base APIRootView class to enforce user authentication.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.views.NautobotAPIVersionMixin" optional hover>NautobotAPIVersionMixin</autoref></code>, <code><autoref identifier="rest_framework.routers.APIRootView" optional hover>APIRootView</autoref></code></p>
+      <p>Extends DRF's base APIRootView class to enforce user authentication.</p>
@@ -10875,10 +10805,10 @@
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.OptInFieldsMixin" href="#nautobot.apps.api.OptInFieldsMixin">OptInFieldsMixin</a></code>, <code><span title="rest_framework.serializers.HyperlinkedModelSerializer">HyperlinkedModelSerializer</span></code></p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.OptInFieldsMixin" optional hover>OptInFieldsMixin</autoref></code>, <code><autoref identifier="rest_framework.serializers.HyperlinkedModelSerializer" optional hover>HyperlinkedModelSerializer</autoref></code></p>
-        <p>This base serializer implements common fields and logic for all ModelSerializers.</p>
+      <p>This base serializer implements common fields and logic for all ModelSerializers.</p>
 <p>Namely, it:</p>
 <ul>
 <li>defines the <code>display</code> field which exposes a human friendly value for the given object.</li>
@@ -10895,11 +10825,6 @@
   <div class="doc doc-children">
@@ -10924,7 +10849,7 @@
     <div class="doc doc-contents ">
-        <p>Return whether this is a nested serializer.</p>
+      <p>Return whether this is a nested serializer.</p>
     </div>
 </div>
@@ -10942,7 +10867,7 @@
     <div class="doc doc-contents ">
-        <p>Instantiate a BaseModelSerializer.</p>
+      <p>Instantiate a BaseModelSerializer.</p>
 <p>The force_csv kwarg allows you to force _is_csv_request() to evaluate True without passing a Request object,
 which is necessary to be able to export appropriately structured CSV from a Job that doesn't have a Request.</p>
@@ -10961,7 +10886,7 @@ which is necessary to be able to export appropriately structured CSV from a Job
     <div class="doc doc-contents ">
-        <p>Return a two tuple of (cls, kwargs) to build a serializer field with.</p>
+      <p>Return a two tuple of (cls, kwargs) to build a serializer field with.</p>
     </div>
@@ -10978,7 +10903,7 @@ which is necessary to be able to export appropriately structured CSV from a Job
     <div class="doc doc-contents ">
-        <p>Create a property field for model methods and properties.</p>
+      <p>Create a property field for model methods and properties.</p>
     </div>
@@ -10995,7 +10920,7 @@ which is necessary to be able to export appropriately structured CSV from a Job
     <div class="doc doc-contents ">
-        <p>Override DRF's default relational-field construction to be app-aware.</p>
+      <p>Override DRF's default relational-field construction to be app-aware.</p>
     </div>
@@ -11012,7 +10937,7 @@ which is necessary to be able to export appropriately structured CSV from a Job
     <div class="doc doc-contents ">
-        <p>Override DRF's default 'url' field construction to be app-aware.</p>
+      <p>Override DRF's default 'url' field construction to be app-aware.</p>
     </div>
@@ -11029,7 +10954,7 @@ which is necessary to be able to export appropriately structured CSV from a Job
     <div class="doc doc-contents ">
-        <p>Prepend or append the given field_name to <code>fields</code> and optionally self.Meta.opt_in_fields as well.</p>
+      <p>Prepend or append the given field_name to <code>fields</code> and optionally self.Meta.opt_in_fields as well.</p>
     </div>
@@ -11046,7 +10971,7 @@ which is necessary to be able to export appropriately structured CSV from a Job
     <div class="doc doc-contents ">
-        <p>Return either the <code>display</code> property of the instance or <code>str(instance)</code></p>
+      <p>Return either the <code>display</code> property of the instance or <code>str(instance)</code></p>
     </div>
@@ -11063,7 +10988,7 @@ which is necessary to be able to export appropriately structured CSV from a Job
     <div class="doc doc-contents ">
-        <p>Override get_field_names() to add some custom logic.</p>
+      <p>Override get_field_names() to add some custom logic.</p>
 <p>Assuming that we follow the pattern where <code>fields = "__all__" for the vast majority of serializers in Nautobot,
 we do not strictly need to use this method to protect against inadvertently omitting standard fields
 like</code>display<code>,</code>created<code>, and</code>last_updated`. However, we continue to do as a bit of redundant safety.</p>
@@ -11096,7 +11021,7 @@ way of <em>excluding</em> fields that we <em>don't</em> want to include by defau
     <div class="doc doc-contents ">
-        <p>Support bulk deletion of objects using the list endpoint for a model. Accepts a DELETE action with a list of one
+      <p>Support bulk deletion of objects using the list endpoint for a model. Accepts a DELETE action with a list of one
 or more JSON objects, each specifying the UUID of an object to be deleted. For example:</p>
 <p>DELETE /api/dcim/locations/
 [
@@ -11107,11 +11032,6 @@ or more JSON objects, each specifying the UUID of an object to be deleted. For e
   <div class="doc doc-children">
@@ -11144,7 +11064,7 @@ or more JSON objects, each specifying the UUID of an object to be deleted. For e
     <div class="doc doc-contents ">
-        <p>Support bulk modification of objects using the list endpoint for a model. Accepts a PATCH action with a list of one
+      <p>Support bulk modification of objects using the list endpoint for a model. Accepts a PATCH action with a list of one
 or more JSON objects, each specifying the UUID of an object to be updated as well as the attributes to be set.
 For example:</p>
 <p>PATCH /api/dcim/locations/
@@ -11162,11 +11082,6 @@ For example:</p>
   <div class="doc doc-children">
@@ -11198,21 +11113,16 @@ For example:</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="rest_framework.serializers.Field">Field</span></code></p>
+              Bases: <code><autoref identifier="rest_framework.serializers.Field" optional hover>Field</autoref></code></p>
-        <p>Represent a ChoiceField as {'value': <DB value>, 'label': <string>}. Accepts a single value on write.</p>
+      <p>Represent a ChoiceField as {'value': <DB value>, 'label': <string>}. Accepts a single value on write.</p>
 <p>:param choices: An iterable of choices in the form (value, key).
 :param allow_blank: Allow blank values in addition to the listed choices.</p>
   <div class="doc doc-children">
@@ -11244,15 +11154,10 @@ For example:</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="rest_framework.relations.RelatedField">RelatedField</span></code></p>
-        <p>Represent a ContentType as '<app_label>.<model>'</p>
+              Bases: <code><autoref identifier="rest_framework.relations.RelatedField" optional hover>RelatedField</autoref></code></p>
+      <p>Represent a ContentType as '<app_label>.<model>'</p>
@@ -11288,15 +11193,10 @@ For example:</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.ValidatedModelSerializer" href="#nautobot.apps.api.ValidatedModelSerializer">ValidatedModelSerializer</a></code></p>
-        <p>Extends ModelSerializer to render any CustomFields and their values associated with an object.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.ValidatedModelSerializer" optional hover>ValidatedModelSerializer</autoref></code></p>
+      <p>Extends ModelSerializer to render any CustomFields and their values associated with an object.</p>
@@ -11322,7 +11222,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Ensure that "custom_fields" and "computed_fields" are included appropriately.</p>
+      <p>Ensure that "custom_fields" and "computed_fields" are included appropriately.</p>
     </div>
@@ -11349,15 +11249,10 @@ For example:</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.views.ModelViewSet" href="#nautobot.apps.api.ModelViewSet">ModelViewSet</a></code></p>
-        <p>Include the applicable set of CustomFields in the ModelViewSet context.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.views.ModelViewSet" optional hover>ModelViewSet</autoref></code></p>
+      <p>Include the applicable set of CustomFields in the ModelViewSet context.</p>
@@ -11393,15 +11288,10 @@ For example:</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="nautobot.core.api.views.NautobotAPIVersionMixin">NautobotAPIVersionMixin</span></code>, <code><a class="autorefs autorefs-internal" title="nautobot.core.api.views.BulkUpdateModelMixin" href="#nautobot.apps.api.BulkUpdateModelMixin">BulkUpdateModelMixin</a></code>, <code><a class="autorefs autorefs-internal" title="nautobot.core.api.views.BulkDestroyModelMixin" href="#nautobot.apps.api.BulkDestroyModelMixin">BulkDestroyModelMixin</a></code>, <code><a class="autorefs autorefs-internal" title="nautobot.core.api.views.ModelViewSetMixin" href="#nautobot.apps.api.ModelViewSetMixin">ModelViewSetMixin</a></code>, <code><span title="rest_framework.viewsets.ModelViewSet">ModelViewSet</span></code></p>
-        <p>Extend DRF's ModelViewSet to support bulk update and delete functions.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.views.NautobotAPIVersionMixin" optional hover>NautobotAPIVersionMixin</autoref></code>, <code><autoref identifier="nautobot.core.api.views.BulkUpdateModelMixin" optional hover>BulkUpdateModelMixin</autoref></code>, <code><autoref identifier="nautobot.core.api.views.BulkDestroyModelMixin" optional hover>BulkDestroyModelMixin</autoref></code>, <code><autoref identifier="nautobot.core.api.views.ModelViewSetMixin" optional hover>ModelViewSetMixin</autoref></code>, <code><autoref identifier="rest_framework.viewsets.ModelViewSet" optional hover>ModelViewSet</autoref></code></p>
+      <p>Extend DRF's ModelViewSet to support bulk update and delete functions.</p>
@@ -11441,11 +11331,6 @@ For example:</p>
   <div class="doc doc-children">
@@ -11467,25 +11352,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Extend rest_framework.generics.GenericAPIView.get_object to allow "pk" lookups to use a composite-key.</p>
-    </div>
-</div>
-<div class="doc doc-object doc-function">
-<h3 id="nautobot.apps.api.ModelViewSetMixin.get_queryset" class="doc doc-heading">
-            <code class="highlight language-python"><span class="n">get_queryset</span><span class="p">()</span></code>
-<a href="#nautobot.apps.api.ModelViewSetMixin.get_queryset" class="headerlink" title="Permanent link">&para;</a></h3>
-    <div class="doc doc-contents ">
-        <p>Attempt to optimize the queryset based on the fields present in the associated serializer.</p>
-<p>See similar logic in nautobot.core.tables.BaseTable.</p>
+      <p>Extend rest_framework.generics.GenericAPIView.get_object to allow "pk" lookups to use a composite-key.</p>
     </div>
@@ -11502,7 +11369,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Runs anything that needs to occur prior to calling the method handler.</p>
+      <p>Runs anything that needs to occur prior to calling the method handler.</p>
 <p>Override of internal Django Rest Framework API.</p>
     </div>
@@ -11520,7 +11387,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Restrict the view's queryset to allow only the permitted objects for the given request.</p>
+      <p>Restrict the view's queryset to allow only the permitted objects for the given request.</p>
 <p>Subclasses (such as nautobot.extras.api.views.JobModelViewSet) may wish to override this.</p>
 <p>Called by initial(), below.</p>
@@ -11549,15 +11416,10 @@ For example:</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="rest_framework.serializers.MultipleChoiceField">MultipleChoiceField</span></code></p>
-        <p>A MultipleChoiceField that renders the received value as a JSON-compatible list rather than a set.</p>
+              Bases: <code><autoref identifier="rest_framework.serializers.MultipleChoiceField" optional hover>MultipleChoiceField</autoref></code></p>
+      <p>A MultipleChoiceField that renders the received value as a JSON-compatible list rather than a set.</p>
@@ -11583,7 +11445,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Overload default choices handling to also accept a callable.</p>
+      <p>Overload default choices handling to also accept a callable.</p>
     </div>
@@ -11610,15 +11472,10 @@ For example:</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="drf_spectacular.openapi.AutoSchema">AutoSchema</span></code></p>
-        <p>Nautobot-specific extensions to drf-spectacular's AutoSchema.</p>
+              Bases: <code><autoref identifier="drf_spectacular.openapi.AutoSchema" optional hover>AutoSchema</autoref></code></p>
+      <p>Nautobot-specific extensions to drf-spectacular's AutoSchema.</p>
@@ -11647,7 +11504,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Custom property for convenience.</p>
+      <p>Custom property for convenience.</p>
     </div>
 </div>
@@ -11668,7 +11525,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Custom property for convenience.</p>
+      <p>Custom property for convenience.</p>
     </div>
 </div>
@@ -11686,7 +11543,7 @@ For example:</p>
     <div class="doc doc-contents ">
-        <p>Get the appropriate description for a given API endpoint.</p>
+      <p>Get the appropriate description for a given API endpoint.</p>
 <p>By default, if a specific action doesn't have its own docstring, and neither does the view class,
 drf-spectacular will walk up the MRO of the view class until it finds a docstring, and use that.
 Most of our viewsets (for better or for worse) do not have docstrings, and so it'll find and use the generic
@@ -11709,7 +11566,7 @@ make an attempt at rendering a basically accurate default description.</p>
     <div class="doc doc-contents ">
-        <p>Nautobot's custom bulk operations, even though they return a list of records, are NOT filterable.</p>
+      <p>Nautobot's custom bulk operations, even though they return a list of records, are NOT filterable.</p>
     </div>
@@ -11726,7 +11583,7 @@ make an attempt at rendering a basically accurate default description.</p>
     <div class="doc doc-contents ">
-        <p>Extend the base method to handle Nautobot's REST API bulk operations.</p>
+      <p>Extend the base method to handle Nautobot's REST API bulk operations.</p>
 <p>Without this extension, every one of our ModelViewSet classes will result in drf-spectacular complaining
 about operationId collisions, e.g. between DELETE /api/dcim/devices/ and DELETE /api/dcim/devices/<pk>/ would
 both get resolved to the same "dcim_devices_destroy" operation-id and this would make drf-spectacular complain.</p>
@@ -11747,7 +11604,7 @@ both get resolved to the same "dcim_devices_destroy" operation-id and this would
     <div class="doc doc-contents ">
-        <p>Return the request serializer (used for describing/parsing the request payload) for this endpoint.</p>
+      <p>Return the request serializer (used for describing/parsing the request payload) for this endpoint.</p>
 <p>We override the default drf-spectacular behavior for the case where the endpoint describes a write request
 with required data (PATCH, POST, PUT). In those cases we replace FooSerializer with a dynamically-defined
 WritableFooSerializer class in order to more accurately represent the available options on write.</p>
@@ -11769,7 +11626,7 @@ require a list of serializers as input, rather than a single one.</p>
     <div class="doc doc-contents ">
-        <p>Return the response serializer (used for describing the response payload) for this endpoint.</p>
+      <p>Return the response serializer (used for describing the response payload) for this endpoint.</p>
 <p>We override the default drf-spectacular behavior for the case where the endpoint describes a write request
 to a bulk endpoint, which returns a list of serializers, rather than a single one.</p>
@@ -11788,7 +11645,7 @@ to a bulk endpoint, which returns a list of serializers, rather than a single on
     <div class="doc doc-contents ">
-        <p>Get the serializer's ref_name Meta attribute if set, or else derive a ref_name automatically.</p>
+      <p>Get the serializer's ref_name Meta attribute if set, or else derive a ref_name automatically.</p>
 <p>Based on drf_yasg.utils.get_serializer_ref_name().</p>
     </div>
@@ -11806,7 +11663,7 @@ to a bulk endpoint, which returns a list of serializers, rather than a single on
     <div class="doc doc-contents ">
-        <p>Given a FooSerializer instance, look up or construct a [Bulk]WritableFooSerializer class if necessary.</p>
+      <p>Given a FooSerializer instance, look up or construct a [Bulk]WritableFooSerializer class if necessary.</p>
 <p>If no [Bulk]WritableFooSerializer class is needed, returns None instead.</p>
     </div>
@@ -11824,7 +11681,7 @@ to a bulk endpoint, which returns a list of serializers, rather than a single on
     <div class="doc doc-contents ">
-        <p>Re-add required <code>id</code> field on bulk_partial_update action.</p>
+      <p>Re-add required <code>id</code> field on bulk_partial_update action.</p>
 <p>drf-spectacular clears the <code>required</code> list for any partial serializers in its <code>_map_basic_serializer()</code>,
 but Nautobot bulk partial updates require the <code>id</code> field to be specified for each object to update.</p>
@@ -11853,15 +11710,10 @@ but Nautobot bulk partial updates require the <code>id</code> field to be specif
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="rest_framework.parsers.BaseParser">BaseParser</span></code></p>
-        <p>Counterpart to NautobotCSVRenderer - import CSV data.</p>
+              Bases: <code><autoref identifier="rest_framework.parsers.BaseParser" optional hover>BaseParser</autoref></code></p>
+      <p>Counterpart to NautobotCSVRenderer - import CSV data.</p>
@@ -11887,7 +11739,7 @@ but Nautobot bulk partial updates require the <code>id</code> field to be specif
     <div class="doc doc-contents ">
-        <p>Parse a single row of CSV data (represented as a dict) into a dict suitable for consumption by the serializer.</p>
+      <p>Parse a single row of CSV data (represented as a dict) into a dict suitable for consumption by the serializer.</p>
 <p>TODO: it would be more elegant if our serializer fields knew how to deserialize the CSV data themselves;
 could we then literally have the parser just return list(reader) and not need this function at all?</p>
@@ -11916,15 +11768,10 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.mixins.WritableSerializerMixin" href="#nautobot.apps.api.WritableSerializerMixin">WritableSerializerMixin</a></code>, <code><span title="rest_framework.serializers.HyperlinkedRelatedField">HyperlinkedRelatedField</span></code></p>
-        <p>Extend HyperlinkedRelatedField to include URL namespace-awareness, add 'object_type' field, and read composite-keys.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.mixins.WritableSerializerMixin" optional hover>WritableSerializerMixin</autoref></code>, <code><autoref identifier="rest_framework.serializers.HyperlinkedRelatedField" optional hover>HyperlinkedRelatedField</autoref></code></p>
+      <p>Extend HyperlinkedRelatedField to include URL namespace-awareness, add 'object_type' field, and read composite-keys.</p>
@@ -11950,7 +11797,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Override DRF's namespace-unaware default view_name logic for HyperlinkedRelatedField.</p>
+      <p>Override DRF's namespace-unaware default view_name logic for HyperlinkedRelatedField.</p>
 <p>DRF defaults to '{model_name}-detail' instead of '{app_label}:{model_name}-detail'.</p>
     </div>
@@ -11968,7 +11815,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Convert potentially nested representation to a model instance.</p>
+      <p>Convert potentially nested representation to a model instance.</p>
     </div>
@@ -11985,7 +11832,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Convert URL representation to a brief nested representation.</p>
+      <p>Convert URL representation to a brief nested representation.</p>
     </div>
@@ -12012,20 +11859,15 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.RelationshipModelSerializerMixin" href="#nautobot.apps.api.RelationshipModelSerializerMixin">RelationshipModelSerializerMixin</a></code>, <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.CustomFieldModelSerializerMixin" href="#nautobot.apps.api.CustomFieldModelSerializerMixin">CustomFieldModelSerializerMixin</a></code>, <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.NotesSerializerMixin" href="#nautobot.apps.api.NotesSerializerMixin">NotesSerializerMixin</a></code>, <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.ValidatedModelSerializer" href="#nautobot.apps.api.ValidatedModelSerializer">ValidatedModelSerializer</a></code></p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.RelationshipModelSerializerMixin" optional hover>RelationshipModelSerializerMixin</autoref></code>, <code><autoref identifier="nautobot.core.api.serializers.CustomFieldModelSerializerMixin" optional hover>CustomFieldModelSerializerMixin</autoref></code>, <code><autoref identifier="nautobot.core.api.serializers.NotesSerializerMixin" optional hover>NotesSerializerMixin</autoref></code>, <code><autoref identifier="nautobot.core.api.serializers.ValidatedModelSerializer" optional hover>ValidatedModelSerializer</autoref></code></p>
-        <p>Base class to use for serializers based on OrganizationalModel or PrimaryModel.</p>
+      <p>Base class to use for serializers based on OrganizationalModel or PrimaryModel.</p>
 <p>Can also be used for models derived from BaseModel, so long as they support custom fields, notes, and relationships.</p>
   <div class="doc doc-children">
@@ -12057,20 +11899,15 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.extras.api.views.NotesViewSetMixin" href="#nautobot.apps.api.NotesViewSetMixin">NotesViewSetMixin</a></code>, <code><a class="autorefs autorefs-internal" title="nautobot.extras.api.views.CustomFieldModelViewSet" href="#nautobot.apps.api.CustomFieldModelViewSet">CustomFieldModelViewSet</a></code></p>
+              Bases: <code><autoref identifier="nautobot.extras.api.views.NotesViewSetMixin" optional hover>NotesViewSetMixin</autoref></code>, <code><autoref identifier="nautobot.extras.api.views.CustomFieldModelViewSet" optional hover>CustomFieldModelViewSet</autoref></code></p>
-        <p>Base class to use for API ViewSets based on OrganizationalModel or PrimaryModel.</p>
+      <p>Base class to use for API ViewSets based on OrganizationalModel or PrimaryModel.</p>
 <p>Can also be used for models derived from BaseModel, so long as they support Notes.</p>
   <div class="doc doc-children">
@@ -12102,15 +11939,10 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.BaseModelSerializer" href="#nautobot.apps.api.BaseModelSerializer">BaseModelSerializer</a></code></p>
-        <p>Extend Serializer with a <code>notes</code> field.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.BaseModelSerializer" optional hover>BaseModelSerializer</autoref></code></p>
+      <p>Extend Serializer with a <code>notes</code> field.</p>
@@ -12136,7 +11968,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Ensure that fields includes "notes_url" field if applicable.</p>
+      <p>Ensure that fields includes "notes_url" field if applicable.</p>
     </div>
@@ -12167,11 +11999,6 @@ could we then literally have the parser just return list(reader) and not need th
   <div class="doc doc-children">
@@ -12194,15 +12021,10 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="nautobot.core.api.authentication.TokenPermissions">TokenPermissions</span></code></p>
-        <p>As nautobot.core.api.authentication.TokenPermissions, but enforcing add_note permission.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.authentication.TokenPermissions" optional hover>TokenPermissions</autoref></code></p>
+      <p>As nautobot.core.api.authentication.TokenPermissions, but enforcing add_note permission.</p>
@@ -12237,7 +12059,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>API methods for returning or creating notes on an object.</p>
+      <p>API methods for returning or creating notes on an object.</p>
     </div>
@@ -12254,7 +12076,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Apply "view" permissions on the POST /notes/ endpoint, otherwise as ModelViewSetMixin.</p>
+      <p>Apply "view" permissions on the POST /notes/ endpoint, otherwise as ModelViewSetMixin.</p>
     </div>
@@ -12281,15 +12103,10 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="rest_framework.serializers.CharField">CharField</span></code></p>
-        <p>Represent the ContentType of this serializer's model as "<app_label>.<model>".</p>
+              Bases: <code><autoref identifier="rest_framework.serializers.CharField" optional hover>CharField</autoref></code></p>
+      <p>Represent the ContentType of this serializer's model as "<app_label>.<model>".</p>
@@ -12315,7 +12132,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Default read_only to True as this should never be a writable field.</p>
+      <p>Default read_only to True as this should never be a writable field.</p>
     </div>
@@ -12332,7 +12149,7 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Get the content-type of this serializer's model.</p>
+      <p>Get the content-type of this serializer's model.</p>
 <p>Implemented this way because <code>_value</code> may be None when generating the schema.</p>
     </div>
@@ -12361,13 +12178,8 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Serializer mixin that adjusts its fields based on the <code>include</code> and <code>exclude_m2m</code> query parameters in a request.</p>
-<p>The serializer's <code>Meta.opt_in_fields</code> controls which fields are influenced by <code>include</code>.</p>
+      <p>A serializer mixin that takes an additional <code>opt_in_fields</code> argument that controls
+which fields should be displayed.</p>
@@ -12396,12 +12208,8 @@ could we then literally have the parser just return list(reader) and not need th
     <div class="doc doc-contents ">
-        <p>Dynamically adjust the dictionary of fields attributed to this serializer instance.</p>
-<ul>
-<li>Removes all serializer fields specified in <code>Meta.opt_in_fields</code> list that aren't specified in the
-  <code>include</code> query parameter. (applies to GET requests only)</li>
-<li>If the <code>exclude_m2m</code> query parameter is truthy, remove all many-to-many serializer fields for performance.</li>
-</ul>
+      <p>Removes all serializer fields specified in a serializers <code>opt_in_fields</code> list that aren't specified in the
+<code>include</code> query parameter.</p>
 <p>As an example, if the serializer specifies that <code>opt_in_fields = ["computed_fields"]</code>
 but <code>computed_fields</code> is not specified in the <code>?include</code> query parameter, <code>computed_fields</code> will be popped
 from the list of fields.</p>
@@ -12432,12 +12240,7 @@ from the list of fields.</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="rest_framework.routers.DefaultRouter">DefaultRouter</span></code></p>
+              Bases: <code><autoref identifier="rest_framework.routers.DefaultRouter" optional hover>DefaultRouter</autoref></code></p>
@@ -12464,7 +12267,7 @@ from the list of fields.</p>
     <div class="doc doc-contents ">
-        <p>Wrap DRF's DefaultRouter to return an alphabetized list of endpoints.</p>
+      <p>Wrap DRF's DefaultRouter to return an alphabetized list of endpoints.</p>
     </div>
@@ -12481,7 +12284,7 @@ from the list of fields.</p>
     <div class="doc doc-contents ">
-        <p>Override DRF's BaseRouter.register() to bypass an unnecessary restriction added in version 3.15.0.</p>
+      <p>Override DRF's BaseRouter.register() to bypass an unnecessary restriction added in version 3.15.0.</p>
 <p>(Reference: https://github.com/encode/django-rest-framework/pull/8438)</p>
     </div>
@@ -12509,15 +12312,10 @@ from the list of fields.</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="nautobot.core.api.views.NautobotAPIVersionMixin">NautobotAPIVersionMixin</span></code>, <code><a class="autorefs autorefs-internal" title="nautobot.core.api.views.ModelViewSetMixin" href="#nautobot.apps.api.ModelViewSetMixin">ModelViewSetMixin</a></code>, <code><span title="rest_framework.viewsets.ReadOnlyModelViewSet">ReadOnlyModelViewSet</span></code></p>
-        <p>Extend DRF's ReadOnlyModelViewSet to support queryset restriction.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.views.NautobotAPIVersionMixin" optional hover>NautobotAPIVersionMixin</autoref></code>, <code><autoref identifier="nautobot.core.api.views.ModelViewSetMixin" optional hover>ModelViewSetMixin</autoref></code>, <code><autoref identifier="rest_framework.viewsets.ReadOnlyModelViewSet" optional hover>ReadOnlyModelViewSet</autoref></code></p>
+      <p>Extend DRF's ReadOnlyModelViewSet to support queryset restriction.</p>
@@ -12553,15 +12351,10 @@ from the list of fields.</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.ValidatedModelSerializer" href="#nautobot.apps.api.ValidatedModelSerializer">ValidatedModelSerializer</a></code></p>
-        <p>Extend ValidatedModelSerializer with a <code>relationships</code> field.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.ValidatedModelSerializer" optional hover>ValidatedModelSerializer</autoref></code></p>
+      <p>Extend ValidatedModelSerializer with a <code>relationships</code> field.</p>
@@ -12587,7 +12380,7 @@ from the list of fields.</p>
     <div class="doc doc-contents ">
-        <p>Ensure that "relationships" is included as an opt-in field on root serializers.</p>
+      <p>Ensure that "relationships" is included as an opt-in field on root serializers.</p>
     </div>
@@ -12614,20 +12407,15 @@ from the list of fields.</p>
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="rest_framework.relations.PrimaryKeyRelatedField">PrimaryKeyRelatedField</span></code></p>
+              Bases: <code><autoref identifier="rest_framework.relations.PrimaryKeyRelatedField" optional hover>PrimaryKeyRelatedField</autoref></code></p>
-        <p>Extends PrimaryKeyRelatedField to return a serialized object on read. This is useful for representing related
+      <p>Extends PrimaryKeyRelatedField to return a serialized object on read. This is useful for representing related
 objects in a ManyToManyField while still allowing a set of primary keys to be written.</p>
   <div class="doc doc-children">
@@ -12659,12 +12447,7 @@ objects in a ManyToManyField while still allowing a set of primary keys to be wr
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.BaseModelSerializer" href="#nautobot.apps.api.BaseModelSerializer">BaseModelSerializer</a></code></p>
+              Bases: <code><autoref identifier="nautobot.core.api.BaseModelSerializer" optional hover>BaseModelSerializer</autoref></code></p>
@@ -12691,7 +12474,7 @@ objects in a ManyToManyField while still allowing a set of primary keys to be wr
     <div class="doc doc-contents ">
-        <p>Ensure that 'tags' field is always present except on nested serializers.</p>
+      <p>Ensure that 'tags' field is always present except on nested serializers.</p>
     </div>
@@ -12718,15 +12501,10 @@ objects in a ManyToManyField while still allowing a set of primary keys to be wr
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><span title="timezone_field.rest_framework.TimeZoneSerializerField">TimeZoneSerializerField</span></code></p>
-        <p>Represents a time zone as a string.</p>
+              Bases: <code><autoref identifier="timezone_field.rest_framework.TimeZoneSerializerField" optional hover>TimeZoneSerializerField</autoref></code></p>
+      <p>Represents a time zone as a string.</p>
     </div>
@@ -12746,15 +12524,10 @@ objects in a ManyToManyField while still allowing a set of primary keys to be wr
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.BaseModelSerializer" href="#nautobot.apps.api.BaseModelSerializer">BaseModelSerializer</a></code></p>
-        <p>Add a <code>tree_depth</code> field to non-nested model serializers based on django-tree-queries.</p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.BaseModelSerializer" optional hover>BaseModelSerializer</autoref></code></p>
+      <p>Add a <code>tree_depth</code> field to non-nested model serializers based on django-tree-queries.</p>
@@ -12780,7 +12553,7 @@ objects in a ManyToManyField while still allowing a set of primary keys to be wr
     <div class="doc doc-contents ">
-        <p>Ensure that "tree_depth" is included on root serializers only, as nested objects are not annotated.</p>
+      <p>Ensure that "tree_depth" is included on root serializers only, as nested objects are not annotated.</p>
     </div>
@@ -12797,7 +12570,7 @@ objects in a ManyToManyField while still allowing a set of primary keys to be wr
     <div class="doc doc-contents ">
-        <p>The <code>tree_depth</code> is not a database field, but an annotation automatically added by django-tree-queries.</p>
+      <p>The <code>tree_depth</code> is not a database field, but an annotation automatically added by django-tree-queries.</p>
     </div>
@@ -12824,20 +12597,15 @@ objects in a ManyToManyField while still allowing a set of primary keys to be wr
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.BaseModelSerializer" href="#nautobot.apps.api.BaseModelSerializer">BaseModelSerializer</a></code></p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.BaseModelSerializer" optional hover>BaseModelSerializer</autoref></code></p>
-        <p>Extends the built-in ModelSerializer to enforce calling full_clean() on a copy of the associated instance during
+      <p>Extends the built-in ModelSerializer to enforce calling full_clean() on a copy of the associated instance during
 validation. (DRF does not do this by default; see https://github.com/encode/django-rest-framework/issues/3144)</p>
   <div class="doc doc-children">
@@ -12869,10 +12637,10 @@ validation. (DRF does not do this by default; see https://github.com/encode/djan
     <div class="doc doc-contents ">
             <p class="doc doc-class-bases">
-              Bases: <code><a class="autorefs autorefs-internal" title="nautobot.core.api.serializers.BaseModelSerializer" href="#nautobot.apps.api.BaseModelSerializer">BaseModelSerializer</a></code></p>
+              Bases: <code><autoref identifier="nautobot.core.api.serializers.BaseModelSerializer" optional hover>BaseModelSerializer</autoref></code></p>
-        <p>Returns a nested representation of an object on read, but accepts either the nested representation or the
+      <p>Returns a nested representation of an object on read, but accepts either the nested representation or the
 primary key value on write operations.</p>
 <p>Note that subclasses will always have a read-only <code>object_type</code> field, which represents the content-type of this
 serializer's associated model (e.g. "dcim.device"). This is required as the OpenAPI schema, using the
@@ -12882,11 +12650,6 @@ which of several possible nested serializers are in use for a given attribute.</
   <div class="doc doc-children">
@@ -12919,7 +12682,7 @@ which of several possible nested serializers are in use for a given attribute.</
     <div class="doc doc-contents ">
-        <p>WritableSerializerMixin provides the to_internal_value() function.
+      <p>WritableSerializerMixin provides the to_internal_value() function.
 The function provides the ability to write API requests that identify unique objects based on
 combinations of fields other than the primary key.
 e.g:
@@ -12930,11 +12693,6 @@ vs
   <div class="doc doc-children">
@@ -12956,7 +12714,7 @@ vs
     <div class="doc doc-contents ">
-        <p>Retrieve an unique object based on a dictionary of data attributes and raise errors accordingly if the object is not found.</p>
+      <p>Retrieve an unique object based on a dictionary of data attributes and raise errors accordingly if the object is not found.</p>
     </div>
@@ -12973,7 +12731,7 @@ vs
     <div class="doc doc-contents ">
-        <p>Data could be a dictionary and an int (for the User model) or a str that represents the primary key.
+      <p>Data could be a dictionary and an int (for the User model) or a str that represents the primary key.
 If it is a dictionary, we return it after remove non-filter fields.
 If it is a primary key, we return a dictionary object formatted like this {"pk": pk}</p>
@@ -12992,7 +12750,7 @@ If it is a primary key, we return a dictionary object formatted like this {"pk":
     <div class="doc doc-contents ">
-        <p>Make output from a WritableSerializer "round-trip" capable by automatically stripping from the
+      <p>Make output from a WritableSerializer "round-trip" capable by automatically stripping from the
 data any serializer fields that do not correspond to a specific model field</p>
     </div>
@@ -13010,7 +12768,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Return an object or a list of objects based on a dictionary of data attributes or an UUID.</p>
+      <p>Return an object or a list of objects based on a dictionary of data attributes or an UUID.</p>
     </div>
@@ -13036,7 +12794,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Translate a dictionary of attributes to a nested set of parameters suitable for QuerySet filtering. For example:</p>
+      <p>Translate a dictionary of attributes to a nested set of parameters suitable for QuerySet filtering. For example:</p>
 <div class="highlight"><pre><span></span><code>{
     &quot;name&quot;: &quot;Foo&quot;,
     &quot;rack&quot;: {
@@ -13069,7 +12827,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Dynamically import a class from an absolute path string</p>
+      <p>Dynamically import a class from an absolute path string</p>
     </div>
@@ -13086,7 +12844,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Returns the serializer of an api_version</p>
+      <p>Returns the serializer of an api_version</p>
 <p><span class="doc-section-title">Parameters:</span></p>
@@ -13101,11 +12859,9 @@ data any serializer fields that do not correspond to a specific model field</p>
       </thead>
       <tbody>
           <tr class="doc-section-item">
+            <td><code>serializer_choices</code></td>
             <td>
-                <code>serializer_choices</code>
-            </td>
-            <td>
-                  <code>tuple</code>
+                  <code><autoref identifier="tuple" optional>tuple</autoref></code>
             </td>
             <td>
               <div class="doc-md-description">
@@ -13117,11 +12873,9 @@ data any serializer fields that do not correspond to a specific model field</p>
             </td>
           </tr>
           <tr class="doc-section-item">
+            <td><code>api_version</code></td>
             <td>
-                <code>api_version</code>
-            </td>
-            <td>
-                  <code>str</code>
+                  <code><autoref identifier="str" optional>str</autoref></code>
             </td>
             <td>
               <div class="doc-md-description">
@@ -13147,7 +12901,7 @@ data any serializer fields that do not correspond to a specific model field</p>
       <tbody>
           <tr class="doc-section-item">
             <td>
-                  <code>Serializer</code>
+                  <code><autoref identifier="Serializer" optional>Serializer</autoref></code>
             </td>
             <td>
               <div class="doc-md-description">
@@ -13173,7 +12927,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Dynamically resolve and return the appropriate serializer for a model.</p>
+      <p>Dynamically resolve and return the appropriate serializer for a model.</p>
 <p><span class="doc-section-title">Raises:</span></p>
@@ -13187,7 +12941,7 @@ data any serializer fields that do not correspond to a specific model field</p>
       <tbody>
           <tr class="doc-section-item">
             <td>
-                  <code>SerializerNotFound</code>
+                  <code><autoref identifier="SerializerNotFound" optional>SerializerNotFound</autoref></code>
             </td>
             <td>
               <div class="doc-md-description">
@@ -13213,7 +12967,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Derive the view name from its associated model, if it has one. Fall back to DRF's built-in <code>get_view_name</code>.</p>
+      <p>Derive the view name from its associated model, if it has one. Fall back to DRF's built-in <code>get_view_name</code>.</p>
     </div>
@@ -13230,7 +12984,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Return True of the request is being made via the REST API.</p>
+      <p>Return True of the request is being made via the REST API.</p>
     </div>
@@ -13247,7 +13001,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Handle exceptions and return a useful error message for REST API requests.</p>
+      <p>Handle exceptions and return a useful error message for REST API requests.</p>
     </div>
@@ -13264,7 +13018,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <div class="doc doc-contents ">
-        <p>Returns appropriate serializer class depending on request api_version, and swagger_fake_view</p>
+      <p>Returns appropriate serializer class depending on request api_version, and swagger_fake_view</p>
 <p><span class="doc-section-title">Parameters:</span></p>
@@ -13279,9 +13033,7 @@ data any serializer fields that do not correspond to a specific model field</p>
       </thead>
       <tbody>
           <tr class="doc-section-item">
-            <td>
-                <code>obj</code>
-            </td>
+            <td><code>obj</code></td>
             <td>
                   <code>ViewSet instance</code>
             </td>
@@ -13295,11 +13047,9 @@ data any serializer fields that do not correspond to a specific model field</p>
             </td>
           </tr>
           <tr class="doc-section-item">
+            <td><code>serializer_choices</code></td>
             <td>
-                <code>serializer_choices</code>
-            </td>
-            <td>
-                  <code>tuple</code>
+                  <code><autoref identifier="tuple" optional>tuple</autoref></code>
             </td>
             <td>
               <div class="doc-md-description">
@@ -13311,11 +13061,9 @@ data any serializer fields that do not correspond to a specific model field</p>
             </td>
           </tr>
           <tr class="doc-section-item">
+            <td><code>default_serializer</code></td>
             <td>
-                <code>default_serializer</code>
-            </td>
-            <td>
-                  <code>Serializer</code>
+                  <code><autoref identifier="Serializer" optional>Serializer</autoref></code>
             </td>
             <td>
               <div class="doc-md-description">
@@ -13486,7 +13234,7 @@ data any serializer fields that do not correspond to a specific model field</p>
     <script id="__config" type="application/json">{"base": "../../..", "features": ["content.code.annotate", "content.code.copy", "content.tabs.link", "navigation.footer", "navigation.tabs", "navigation.tabs.sticky", "navigation.tracking", "search.highlight", "search.share", "search.suggest"], "search": "../../../assets/javascripts/workers/search.6ce7567c.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}}</script>
-      <script src="../../../assets/javascripts/bundle.88dd0f4e.min.js"></script>
+      <script src="../../../assets/javascripts/bundle.83f73b43.min.js"></script>
         <script src="https://code.jquery.com/jquery-3.7.1.min.js"></script>