Skip to content

[Notifier][Mercure] Document options in README file #60259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 7.4
Choose a base branch
from

Conversation

alamirault
Copy link
Contributor

Q A
Branch? 7.3
Bug fix? no
New feature? no
Deprecations? no
Issues Fix #...
License MIT

Document mercure notifier options in component readme (as others)

symfony/symfony-docs#20857

@alamirault alamirault force-pushed the feature/20857-document-mercure-options branch from 9c70369 to 2235584 Compare May 9, 2025 09:06
@OskarStark OskarStark changed the title [Notifier] Document Notifier Mercure options in README file [Notifier][Mercure] Document options in README file May 9, 2025
@fabpot fabpot modified the milestones: 7.3, 7.4 May 26, 2025

$chatMessage = new ChatMessage('Contribute To Symfony');

$options = new MercureOptions(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that we decided to not use named arguments in Symfony Docs, could we please add a short comment to explain what does each option mean in this code example? Thanks!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's also because MercureOptions is diverging from the other option classes
the norm is to have a constructor with only array $options and to then have fluent setters, see existing classes for inspiration
it'd be nice to check all option classes and add some consistency - looks like it might be needed 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants