Closed netux closed 1 year ago
Describe the bug The JS WrongFilePathLinter may trip up when trying to find the file of a class path generated dynamically using string literals.
In my case, I have the following function:
loadFragmentRelative(fragmentName) { return this.loadFragment({ name: `com.mycompany.myapp.view.${fragmentName}` }); }
To Reproduce Steps to reproduce the behavior:
`com.mycompany.myapp.${someValue}`
Expected behavior I'd rather WrongFilePathLinter skip this error.
Screenshots N/A
Desktop (please complete the following information):
Additional context This may also happen with normal string concatenation. E.g.:
"com.mycompany.myapp." + someValue
Project attachment N/A. I don't think it is needed.
Fixed, please check
Solved. Thank you!
Describe the bug The JS WrongFilePathLinter may trip up when trying to find the file of a class path generated dynamically using string literals.
In my case, I have the following function:
To Reproduce Steps to reproduce the behavior:
Expected behavior I'd rather WrongFilePathLinter skip this error.
Screenshots N/A
Desktop (please complete the following information):
Additional context This may also happen with normal string concatenation. E.g.:
Project attachment N/A. I don't think it is needed.