<commit_before><h2>Route Constraints</h2>

<p>The following three constraints apply to route names. They will only work with <code>\{{liquid-outlet}}</code> because only <code>\{{liquid-outlet}}</code> has visibility into routes. (The other helpers like <code>\{{liquid-if}}</code>) don't know anything about routes.)</p>

<dl class="dl-horizontal">
  <dt>fromRoute</dt>
  <dd>Matches the route name at the start of a transition.</dd>

  <dt>toRoute</dt>
  <dd>Matches the route name at the end of a transition.</dd>

  <dt>withinRoute</dt>
  <dd>Matches the same name at both the start and end of the
    transition. This is good for matching transitions that are not
    route changes.
  </dd>
</dl>

<p>Each of them accepts one argument. The argument can be a string
route name, a function that tests route names, or a list of either of
those.</p>

<p>The next three constraint apply to routes' models. They too only
work with <code>\{{liquid-outlet}}</code>.</p>

<dl class="dl-horizontal">
  <dt>fromModel</dt>
  <dd>Matches the route's model at the start of a transition.</dd>

  <dt>toModel</dt>
  <dd>Matches the route's model at the start of a transition.</dd>

  <dt>betweenModels</dt>
  <dd>A shorthand for both fromModel and toModel.</dd>
</dl>

<p>Each of them accepts a function for testing the model, which
receives the model as its first argument and should return a
boolean. You have optional access to the <em>other</em> model in the
second argument (that is, a <code>fromModel</code> matcher receives <code>(oldModel, newModel)</code> and a <code>toModel</code> matcher receives <code>(newModel, oldModel)</code>).</p>
<commit_msg>Fix typo in Documentation website<commit_after><h2>Route Constraints</h2>

<p>The following three constraints apply to route names. They will only work with <code>\{{liquid-outlet}}</code> because only <code>\{{liquid-outlet}}</code> has visibility into routes. (The other helpers like <code>\{{liquid-if}}</code>) don't know anything about routes.)</p>

<dl class="dl-horizontal">
  <dt>fromRoute</dt>
  <dd>Matches the route name at the start of a transition.</dd>

  <dt>toRoute</dt>
  <dd>Matches the route name at the end of a transition.</dd>

  <dt>withinRoute</dt>
  <dd>Matches the same name at both the start and end of the
    transition. This is good for matching transitions that are not
    route changes.
  </dd>
</dl>

<p>Each of them accepts one argument. The argument can be a string
route name, a function that tests route names, or a list of either of
those.</p>

<p>The next three constraint apply to routes' models. They too only
work with <code>\{{liquid-outlet}}</code>.</p>

<dl class="dl-horizontal">
  <dt>fromModel</dt>
  <dd>Matches the route's model at the start of a transition.</dd>

  <dt>toModel</dt>
  <dd>Matches the route's model at the end of a transition.</dd>

  <dt>betweenModels</dt>
  <dd>A shorthand for both fromModel and toModel.</dd>
</dl>

<p>Each of them accepts a function for testing the model, which
receives the model as its first argument and should return a
boolean. You have optional access to the <em>other</em> model in the
second argument (that is, a <code>fromModel</code> matcher receives <code>(oldModel, newModel)</code> and a <code>toModel</code> matcher receives <code>(newModel, oldModel)</code>).</p>

{'fraction_non_alphanumeric': 0.12658227848101267, 'fraction_numerical': 0.0012055455093429777, 'mean_word_length': 4.379254457050243, 'pattern_counts': {'":': 0, '<': 115, '<?xml version=': 0, '>': 115, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3401596', 'n_tokens_mistral': 1053, 'n_tokens_neox': 1006, 'n_words': 420}