Wrong formatting of object literal inside ternary operator when using tabs

[FlameWolf]

Prettier 2.6.0
Playground link

# Options (if any):
--use-tabs

Input:

const flag = true;
const response = flag ? {
    name: "Jane Doe",
    age: 32
  } : {
    name: "John Doe",
    age: 23
  };

Output:

const flag = true;
const response = flag
	? {
			name: "Jane Doe",
			age: 32
	  }
	: {
			name: "John Doe",
			age: 23
	  };

Expected behavior:

• The closing curly braces should not have leading spaces
• The code inside the curly braces should have one fewer tabs of indentation

const flag = true;
const response = flag
	? {
		name: "Jane Doe",
		age: 32
	}
	: {
		name: "John Doe",
		age: 23
	};

[importantaffairs]

Thanks for opening this. I'm also having this issue on version 2.6.1

[aradalvand]

Same issue here on v2.7.1. No updates still?!

[james-lawrence]

piling on with another example:

	maybe<T>(key: string, lookup: () => Promise<T>, ...options: option[]): Promise<T> {
		const found = this.get<T>(key)
		return found ? Promise.resolve(found) : lookup().then((v: T) => {
			this.set(key, v, ...options)
			return v
		})
	}

[dylemma]

I'm seeing similar behavior in 3.1.1, but but my closing } are not aligned to the opening { like in OP's example; they're just indented by an extra tab. I think I'd prefer aligning the } with spaces over this:

playground

Input

someCondition ? 
	{ 
		a: 1, 
		b: 2
	} : { 
		c: 3
	}

Output

someCondition
	? {
			a: 1,
			b: 2,
		}
	: {
			c: 3,
		};

It also seems to over-indent the closing syntax for functions when they appear in a ternary: playground

[dylemma]

I think the correct behavior here would be to align the { and } with each other via spaces after the indentation tabs. And for the "middle" lines I think you would probably want three spaces followed by a tab, e.g.

someCondition
	? {
	  	a: 1,
	  	b: 1,
	  }
	: {
	  	c: 3,
	  }

Admittedly it feels weird for a line to contain \t \t but this approach results in something the should look "right" no matter what the viewer's tab-width is configured to, even for small widths like 1 or 2 spaces.

[thisjt]

I think the correct behavior here would be to align the { and } with each other via spaces after the indentation tabs. And for the "middle" lines I think you would probably want three spaces followed by a tab, e.g.

someCondition
	? {
	  	a: 1,
	  	b: 1,
	  }
	: {
	  	c: 3,
	  }

Admittedly it feels weird for a line to contain \t \t but this approach results in something the should look "right" no matter what the viewer's tab-width is configured to, even for small widths like 1 or 2 spaces.

Sadly this does not work if useTabs are set to true as prettier removes the spaces and reapplies the incorrect tabbing format.

I'm surprised that this has been an issue since 2018 yet there has not been any updates or attempts with fixing this bug.

#4203