Incorrect newline indentation in struct literals
See original GitHub issueWhen typing a struct literal, pressing Enter at the end of the last field line does not indent the new empty line correctly.
For example:
SomeStruct {
foo: 1,
bar: 2,<cursor>
}
Pressing Enter at <cursor>
results in the following:
SomeStruct {
foo: 1,
bar: 2,
<cursor>
}
Whereas I would expect this instead:
SomeStruct {
foo: 1,
bar: 2,
<cursor>
}
I believe this was working in an earlier version of the plugin. I’m currently using v0.1.0.2064.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Keeping code structure with string literal that uses whitespace
If I have a multi-line string literal in my program, is there anyway to keep the indentation of my code consistent without adding...
Read more >`mandatory_comma: true` incorrectly indents the next line at ...
Comma is inserted after "b" and square bracket on line below is indented to the same level as the array element. A subsequent...
Read more >[Review] SE-0168: Multi-Line String Literals - Swift Forums
Hello Swift community, The review of SE-0168 "Multi-Line String Literals" begins now ... or a newline and indentation, between array and dictionary literal...
Read more >Appendix: YAML Techniques - Helm
Appendix: YAML Techniques. Most of this guide has been focused on writing the template language. Here, we'll look at the YAML format. YAML...
Read more >Zig Language Reference
This syntax tells the Zig compiler that the function will either return an error or a value. An error union type combines an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, confirmed that it works.
Yeah, I think this was fixed in https://github.com/intellij-rust/intellij-rust/commit/9e91420da18de2fe547c02cce6c21748fc7256b0