doc comment forces multiline exceptions
- type
exception Foo({name: string, msg: string})and run formatter - notice still single line
- add doc comment:
/** foo */
exception Foo({name: string, msg: string})
and run formatter 4. notice how formatter forces multiline:
/** foo */
exception Foo({
name: string,
msg: string,
})
see also #7946
Just a side note - I don't think we can call these formatter things bugs. It's a formatter behavior that's intentional. You can agree or disagree of course, and there might be good reason to change it, but it's not a bug per se.
Just a side note - I don't think we can call these formatter things bugs. It's a formatter behavior that's intentional. You can agree or disagree of course, and there might be good reason to change it, but it's not a bug per se.
thanks. it's unexpected behavior and there's no way for me to know if it's intentional. would you like me to not open issues on these oddities? or if you want me to, what do you want me to call them?
also if this is indeed intentional, feel free to close this. :)
You don't need to mark them at all, we can do that as we process it. Just describe what you've found and what you expected, and we can label it appropriately from there.
Is this also the case with type (records, inline in variant)?
Is this also the case with
type(records, inline in variant)?
no, just exception