Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[PropertyAccess] Document nullsafe operator usage #17288

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

Conversation

fsoedjede
Copy link
Contributor

@fsoedjede fsoedjede force-pushed the 34483-document-property-access-nullsafe-operator-usage branch from 976033c to 6a5d2ee Compare September 22, 2022 22:56
@javiereguiluz javiereguiluz added PropertyAccess Waiting Code Merge Docs for features pending to be merged labels Sep 23, 2022
@javiereguiluz javiereguiluz added this to the next milestone Sep 23, 2022
@carsonbot carsonbot changed the title [WCM][PropertyAccess] Document nullsafe operator usage [PropertyAccess] [WCM] Document nullsafe operator usage Sep 23, 2022
fabpot added a commit to symfony/symfony that referenced this pull request Oct 1, 2022
…s (fsoedjede)

This PR was merged into the 6.2 branch.

Discussion
----------

[Form][PropertyAccess] Allow optional property accesses

| Q             | A
| ------------- | ---
| Branch?       | 6.2
| Bug fix?      | no
| New feature?  | yes <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | yes <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | Fix #34483 <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT
| Doc PR        | symfony/symfony-docs#17288 <!-- required for new features -->
<!--
Replace this notice by a short README for your feature/bugfix.
This will help reviewers and should be a good start for the documentation.

Additionally (see https://symfony.com/releases):
 - Always add tests and ensure they pass.
 - Bug fixes must be submitted against the lowest maintained branch where they apply
   (lowest branches are regularly merged to upper ones so they get the fixes too).
 - Features and deprecations must be submitted against the latest branch.
 - For new features, provide some code snippets to help understand usage.
 - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
 - Never break backward compatibility (see https://symfony.com/bc).
-->

This PR is basically a copy of #34497 with some minor changes.

I needed it and I have some time now to help advance in implementing it.

**TODO**

- [x] Add nullsafe operator usage
- [x] Update unit test
- [x] Update documentation

Regards

Commits
-------

6455feb feature #34483 - Allow optional property accesses
symfony-splitter pushed a commit to symfony/form that referenced this pull request Oct 1, 2022
…s (fsoedjede)

This PR was merged into the 6.2 branch.

Discussion
----------

[Form][PropertyAccess] Allow optional property accesses

| Q             | A
| ------------- | ---
| Branch?       | 6.2
| Bug fix?      | no
| New feature?  | yes <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | yes <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | Fix #34483 <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT
| Doc PR        | symfony/symfony-docs#17288 <!-- required for new features -->
<!--
Replace this notice by a short README for your feature/bugfix.
This will help reviewers and should be a good start for the documentation.

Additionally (see https://symfony.com/releases):
 - Always add tests and ensure they pass.
 - Bug fixes must be submitted against the lowest maintained branch where they apply
   (lowest branches are regularly merged to upper ones so they get the fixes too).
 - Features and deprecations must be submitted against the latest branch.
 - For new features, provide some code snippets to help understand usage.
 - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
 - Never break backward compatibility (see https://symfony.com/bc).
-->

This PR is basically a copy of #34497 with some minor changes.

I needed it and I have some time now to help advance in implementing it.

**TODO**

- [x] Add nullsafe operator usage
- [x] Update unit test
- [x] Update documentation

Regards

Commits
-------

6455febec6 feature #34483 - Allow optional property accesses
@fsoedjede fsoedjede marked this pull request as ready for review October 1, 2022 16:59
@carsonbot carsonbot modified the milestones: next, 6.2 Oct 1, 2022
@fsoedjede fsoedjede changed the title [PropertyAccess] [WCM] Document nullsafe operator usage [PropertyAccess] Document nullsafe operator usage Oct 1, 2022
@javiereguiluz javiereguiluz added Status: Reviewed and removed Status: Needs Review Waiting Code Merge Docs for features pending to be merged labels Oct 4, 2022
@javiereguiluz javiereguiluz modified the milestones: next, 6.2 Oct 4, 2022
@javiereguiluz javiereguiluz merged commit dabd9ce into symfony:6.2 Oct 4, 2022
@javiereguiluz
Copy link
Member

Felix, thanks a lot for this contribution.

Please note that while merging we made some changes: we moved some contents and introduced some rewords (see 4c55db3) but most of your original contribution remained. Thanks!

@fsoedjede fsoedjede deleted the 34483-document-property-access-nullsafe-operator-usage branch October 6, 2022 21:06
@fsoedjede
Copy link
Contributor Author

No problem @javiereguiluz
The rewording looks better.
Thanks

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.

3 participants