Move Property Mapper from Extbase Fluid Book

[linawolf]

Releases: main, 11.5

[brotkrueml]

I am not sure if the PropertyMapping should go under the Controller folder. As I have no experience with property mapping by now, I assume it can also be used independent of a controller. Maybe "Model / Domain" would be better as it is about mapping of models?

[linawolf]

I am not sure if the PropertyMapping should go under the Controller folder. As I have no experience with property mapping by now, I assume it can also be used independent of a controller. Maybe "Model / Domain" would be better as it is about mapping of models?

I think Property Mapping is one very important feature of the Extbase Controller. One of the things that makes it so useful.

[brotkrueml]

I think Property Mapping is one very important feature of the Extbase Controller. One of the things that makes it so useful.

Fine, then I have to dig into and use it :-)

[brotkrueml]

I don't like the blog_example to be used here. First: The code is not found in the blog_example repository. Second: It introduces dependencies (like the AbstractController from blog_example) which are not necessary for this chapter. Maybe we should provide the code snippets via EXT:examples or just describe it with "my_extension" without generating snippets automatically. What do you think?

I also suggest to integrate the second snippet (injection) into the first one with proper comments.

[linawolf]

The code is found in the blog_example for v12. The snippets where automatically created from them.

Taking the code-snippets from the extension gurantees that they contain valid PHP and can be testet. Also it is the same example used all over. So readers don't have to get used to another extension just for the property mapper.

Yeah, dont like that AbstractController either, I will get rid of it in one of the next steps. Then this example will automatically change as well.

[github-actions]

The backport to 11.5 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 53712e56... Include real code
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

stdout

[backport-2074-to-11.5 b5a0f7d5] Move Property Mapper from Extbase Fluid Book
 Author: lina.wolf <[email protected]>
 Date: Wed Aug 17 16:34:35 2022 +0200
 1 file changed, 105 insertions(+)
 create mode 100644 Documentation/ExtensionArchitecture/Extbase/Reference/Controller/PropertyMapping.rst
[backport-2074-to-11.5 08b2f7df] Update Documentation/ExtensionArchitecture/Extbase/Reference/Controller/PropertyMapping.rst
 Author: Lina Wolf <[email protected]>
 Date: Sat Aug 20 08:55:30 2022 +0200
 1 file changed, 1 insertion(+), 1 deletion(-)
Auto-merging Documentation/CodeSnippets/Config/Extbase.php
CONFLICT (content): Merge conflict in Documentation/CodeSnippets/Config/Extbase.php

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-11.5 11.5
# Navigate to the new working tree
cd .worktrees/backport-11.5
# Create a new branch
git switch --create backport-2074-to-11.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick e6a3a384274e9d70cc862320bcc3292d85dcbf08,01a41812ff9375279a5c08855573a63a3fe7828b,53712e564a67784dd90fd5e6db67fd44655f4f9e,b3705a0d75c272eea9f8af53b6cc329bd44340b2
# Push it to GitHub
git push --set-upstream origin backport-2074-to-11.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-11.5

Then, create a pull request where the base branch is 11.5 and the compare/head branch is backport-2074-to-11.5.