[Feature]: Unify Setting Key and Path

[cancan101]

Feature description

Currently the Path is specified on the "Resolver":

but the Key is specified as a Mapping:

I suggest adding the ability to set the Path using the mapping as well. This would (a) allow for consistency of config and more importantly (b) allow using the transforms to compose the path. Currently we ave to maintain logic outside of the importer since the path needs to be a specific field in the file.

[fashxp]

I like the idea, but isn't the mapping (as it is right now) too late for the path as the path is needed during resolving?

Probably we would need a resolver strategy that also provides (at least a subset) of the mapping functionality?

[cancan101]

I was thinking for "Element Creation" resolver, you could just use the "static path" resolver (presumably with a path that exists) and then the final path would be set by the data target. ie the Object might momentarily be created with a different path but then would be moved to a final location.

[fashxp]

Nice idea 👍

[github-actions]

Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.