spring-projects / spring-projects/spring-tools
Double backslash in application.properties marked invalid (M12)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
In M10, the below line from a properties file is valid ...
my.property=c:\\path\\to\\file
In M12 it is not, and you get warnings such as ...
- missing LineBreak at 't'
- missing LineBreak at '\'
- missing LineBreak at 'f'
- missing LineBreak at '\'
- missing LineBreak at 'p'
- missing LineBreak at '\'
Not a huge issue, but thought it should be raised as it is a regression. I suspect it has something do with the below from the M12 changelog ...
"(Eclipse) default editors for Boot properties (application.properties and application.yml files) now based on the generic editor and the language server support - the old editors are still around, but will be removed in future versions of STS4"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the M12 warning with the application.properties line my.property=c:\\path\\to\\file, then compare it with M10 behavior. Start by investigating the generic editor and language server support mentioned in the changelog; done means this valid escaped path is accepted without the reported warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100