<!-- 🚀 Thank you for contributing! -->
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
Amends the `UserNameMigration` code example in the "Model Coupling"
section of the Schema documentation with correct syntax. Added closing
square brackets to the dictionary literals passed into
`QueryBuilder.set(_ data:)` in multiple places.
<!-- 🚀 Thank you for contributing! -->
This PR updates the documentation to the latest version of Vapor
Toolbox, which added Linux distribution via Homebrew and removed some
deprecated commands
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
---------
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
A reference to .sql() was added to the Field Constraint list so that
anyone who is looking for any other options knows there is the
possibility to use SQLKit.
<!-- 🚀 Thank you for contributing! -->
There was a "in" keyword missing in the post route example for signing
JWTs. The keyword was simply added to the code snippet.
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
---------
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
This PR updates the English Heroku documentation to better reflect the
current database pricing naming scheme at Heroku.
<!-- 🚀 Thank you for contributing! -->
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
<!-- 🚀 Thank you for contributing! -->
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
In the docs section for Vapor Queues, update the link to
`QueuesFluentDriver` to link to the most recent iteration forked and
hosted under the `vapor-community` organization.
Update of custom validator documentation in Spanish from the issue
#1041.
---------
Co-authored-by: TheHandyOwl <24987271+TheHandyOwl@users.noreply.github.com>
NEW: translation EN (current websockets.md file) to ES (new
websockets.es.md file)
---------
Co-authored-by: Ale Mohamad ⌘ <alejandro.mohamad@gmail.com>
<!-- 🚀 Thank you for contributing! -->
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
---------
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
<!-- 🚀 Thank you for contributing! -->
<!-- Describe your changes clearly and use examples if possible. -->
Adds new Tracing chapter to document API introduced in
https://github.com/vapor/vapor/pull/3253
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
<!-- 🚀 Thank you for contributing! -->
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
<!-- 🚀 Thank you for contributing! -->
<!-- Describe your changes clearly and use examples if possible. -->
<!-- When this PR is merged, the title and body will be -->
<!-- used to generate a release automatically. -->
---------
Co-authored-by: Zsolt Váradi <1783465+vzsg@users.noreply.github.com>
### Line break for options:
Added a visual line break to separate the header "Some text options:"
from the list items. This ensures proper Markdown rendering and improves
readability.
---
### Before:
Some text options:
- Example 1
- Example 2
**Rendered as:**
Some text options: - Example 1 - Example 2
---
### After:
Some text options:
(line break added)
- Example 1
- Example 2
**Rendered as:**
Some text options:
- Example 1
- Example 2
---
### Consistent visual rendering across other Markdown elements:
This change introduces a similar visual line break strategy for
informational blocks.
These adjustments ensure uniformity, improve Markdown rendering, and
maintain a cleaner visual structure across various platforms.