docs: document socket ID retrieval for broadcast()->toOthers() with framework adapters#11200
Closed
hectorgrecco wants to merge 108 commits into
Closed
docs: document socket ID retrieval for broadcast()->toOthers() with framework adapters#11200hectorgrecco wants to merge 108 commits into
hectorgrecco wants to merge 108 commits into
Conversation
Removed redundant SalesCoach instantiation example.
* Remove deprecated MCP tools from documentation * Update boost.md
* Documents `Pint/phpdoc_type_annotations_only` * Adjusts markdown * Adjusts tone * adjusts * fix diff --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
…vel#11090) * Add documentation for the new string helper initials introduced in PR laravel/framework#59230 * update docs --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Add Laravel Boost MCP server to upgrade guide note * Fix OpenCode casing in upgrade guide * Update upgrade.md * Update upgrade.md --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
laravel#11103) * Update installation instructions for Laravel Boost to include support for Laravel 13 * feat: Update Boost can be installed * Update ai.md * Update installation.md --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Added exmples to 'host' request properties * Update requests.md updated HTTP requests back to the correct spelling * Update requests.md --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Add Cloudflare email setup * formatting --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Document MCP Apps support * formatting --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
…traints (laravel#11174) The dimensions validation rule supports min_ratio and max_ratio constraints as well as minRatio, maxRatio, and ratioBetween fluent methods, but these were missing from the documentation.
to add a touch of consistency, only document the array based validation rule definitions. the arrays definitions _always_ work, while there are specific situations (regex, fluent rules) where the delimited strings struggle. the DX of the 2 options is similar, although I'd argue in favor of true arrays since with longer ones we can get IDE niceties like autoformatted multiline. By documenting it this way it will encourage new users to the FW to only use the array style. - __always__ use arrays for rule defintions - __never__ use pipe (`|`) delimited strings for rule definitions - standardize `$validatedData` variable name to `$validated`
Now there's three starter kits, and not two, it doesn't make sense to say "Both of these starter kits..."
Signed-off-by: ajiho <lujiahao@88.com>
* update fortify docs * add config note * update fortify.md * minor formatting * formatting --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
This part was wrongly updated on this PR : https://github.com/laravel/docs/pull/11102/changes [Support policy](https://laravel.com/docs/13.x/releases#support-policy) refers to `12.x` for oldest version which allow bug fixes.
This commit orders all of our polymorphic table columns with `*_type` first and `*_id` second.
This matches how the columns are actually generated by the migration helper methods:
```php
$table->nullableulidMorphs('nullableulidMorphs');
$table->ulidMorphs('ulidMorphs');
$table->uuidmorphs('uuidmorphs');
$table->nullableUuidMorphs('nullableUuidMorphs');
$table->morphs('morphs');
$table->nullableMorphs('nullableMorphs');
```
results in:
- nullableulidMorphs_type
- nullableulidMorphs_id
- ulidMorphs_type
- ulidMorphs_id
- uuidmorphs_type
- uuidmorphs_id
- nullableUuidMorphs_type
- nullableUuidMorphs_id
- morphs_type
- morphs_id
- nullableMorphs_type
- nullableMorphs_id
This will help encourage consistency between morph columns generated by the helpers, and any the user may manually define.
I think it also makes sense from a readability standpoint; Comment 5, Tag 17, etc.
Added examples for clickWhenVisible and clickWhenEnabled methods in Dusk documentation.
…ramework adapters
Author
|
Closing — reopening against 13.x branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends the existing "Only To Others - Configuration" section to document how to retrieve the socket ID when using the framework adapter packages (
@laravel/echo-react,@laravel/echo-vue,@laravel/echo-svelte).Previously, this section only showed the vanilla Echo approach (
Echo.socketId()), leaving framework adapter users without guidance — which led to confusion and workarounds (see laravel/echo#474).What's added
echo().socketId()via the exportedecho()helper, for interceptor setup and outside-component usageuseSocketId()reactive hook/composable/rune for inside-component usage, with examples for all three adaptersRelated
useSocketId()hook itself)