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.

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

[Feature Request] Support path splitting based on the result of Apache Velocity operation #19

Closed
iwb-cgalvarez opened this issue Feb 15, 2024 · 1 comment

Comments

@iwb-cgalvarez
Copy link

Use case

As a developer, I would like to be able to convert all the symbols from the value of a Placeholder into ., so the plugin can split the result of the operation into different folders. Let's give an example:

  1. Value of Placeholder $FEATURE_NAME=test-demo
  2. ${FEATURE_NAME.replaceAll("[^\w]", ".")} returns test.demo
  3. The plugin splits test and demo into different folders making test the parent of demo (test/demo)

Current behaviour

Consider that in the folder tree definition of our module templates we have this Apache velocity code:

Screenshot 2024-02-15 at 10 21 42

So we have the following configurations:

Screenshot 2024-02-15 at 10 28 00

When input is:

Screenshot 2024-02-15 at 10 28 56

First the operation seems correct, since the first window is returning test.demo:

Screenshot 2024-02-15 at 10 29 52

But after clicking Finish button, the folder split is broken:

Screenshot 2024-02-15 at 10 30 44

I think the problem here is that instead of splitting the folders based on the result of the apache velocity (which is test.demo) is doing the split based on the whole literal definition (so the function with the dots in the middle "${FEATURE_NAME.replaceAll("[^\\w]", ".")}").

Do you think it's something you could consider adding?

Thank you very much in advance 🙏

@dengzii
Copy link
Owner

dengzii commented Feb 21, 2024

🙏 Thank you for bug report, this problem is fixed in v1.6.6 🎉 .

You can download it at GitHub Release or waiting for IDE's plugin update notification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants