Skip to content
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.

Sign up for GitHub

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

[Documentation] Just a hint... #77

Merged
merged 2 commits into from
Aug 12, 2024
Merged

[Documentation] Just a hint... #77

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2028321
Do not want to forget this hint anymore
mike4git Aug 9, 2024
610a8c6
Update docs/usage.md
mike4git Aug 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -376,6 +376,22 @@ person.addresses.populator:

There is no new converter but a different populator implementation for this.

### PropertyMappingPopulator & ArrayPropertyMappingPopulator

#### Closure based upon your converter

If you need a Closure which is based upon this Converter (e.g. for PropertyMappingPopulation) you can declare it in this
way and use it in the `PropertyMappingPopulator` configuration as argument for `$mapper`:

```yaml
converter.closure.factory:
class: \Closure
factory: [ '\Closure', 'fromCallable' ]
arguments:
- '@my.converter'
- 'convert'
mike4git marked this conversation as resolved.
Show resolved Hide resolved
```

## Context

Sometimes you will need parameterized conversion which is not depending on the objects themselves.
Expand Down