Feature/refactor

[andreicek]

Please check if the PR fulfills these requirements

• [x] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

• [x] Bugfix
• [x] Feature
• [x] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

In mapAssetPath you would have received outputPath that you shouldn't worry about at all.

What is the new behavior?

Now there are three arguments in the mapAssetPath: requirePath, assetName, isChunk.

Does this PR introduce a breaking change?

• [x] Yes
• [ ] No

If this PR contains a breaking change, please describe the following...

• Impact: mapAssetPath no longer working with the second argument as expected.
• Migration path for existing applications: Remove/revise logic that is utilising assetName
• Github Issue(s) this is regarding:

Other information: