Skip to content

Commit

Permalink
deploy: 8963db3
Browse files Browse the repository at this point in the history
  • Loading branch information
jcrist committed Oct 13, 2024
1 parent a8a3a92 commit 47a8a73
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion _sources/structs.rst.txt
Original file line number Diff line number Diff line change
Expand Up @@ -725,7 +725,7 @@ Renaming Fields
---------------

Sometimes you want the field name used in the encoded message to differ from
the name used your Python code. Perhaps you want a ``camelCase`` naming
the name used by your Python code. Perhaps you want a ``camelCase`` naming
convention in your JSON messages, but to use ``snake_case`` field names in
Python.

Expand Down
2 changes: 1 addition & 1 deletion structs.html
Original file line number Diff line number Diff line change
Expand Up @@ -944,7 +944,7 @@ <h2>Frozen Instances<a class="headerlink" href="#frozen-instances" title="Permal
<section id="renaming-fields">
<h2>Renaming Fields<a class="headerlink" href="#renaming-fields" title="Permalink to this heading"></a></h2>
<p>Sometimes you want the field name used in the encoded message to differ from
the name used your Python code. Perhaps you want a <code class="docutils literal notranslate"><span class="pre">camelCase</span></code> naming
the name used by your Python code. Perhaps you want a <code class="docutils literal notranslate"><span class="pre">camelCase</span></code> naming
convention in your JSON messages, but to use <code class="docutils literal notranslate"><span class="pre">snake_case</span></code> field names in
Python.</p>
<p><code class="docutils literal notranslate"><span class="pre">msgspec</span></code> supports two places for configuring a field’s name used for
Expand Down

0 comments on commit 47a8a73

Please sign in to comment.