String completions are inconsistent between JSX attributes and JSX expressions

[Andarist]

🔎 Search Terms

string completions jsx attribute expression

🕗 Version & Regression Information

• This is the behavior in every version I tried

⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.3.0-dev.20231023#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgIilQ3wG4BYAKCoBMk0AbFIuTAVwDsNgIO4AVJAGcYACjA4wQgFxwA3nAkQws-CnxwAvgEpZHNgwYVKdRsyStO3XgOFilU2QoeqARhp16DRqlQA8giKKkgC8+BoA9AB8pHAREXAA5CiJcAA+Sa6J-oHwDiFy4ZpxMXEJydmUQA

💻 Code

import React from "react";

declare function Test(props: { prop: "a" }): null;
declare function Test(props: { prop: "b" }): null;

<Test prop="" />; // 'a' | 'b'
<Test prop={""} />; // 'a'

🙁 Actual behavior

Both sites provide different completions.

🙂 Expected behavior

Both of those sites represent the very same JS code and they should provide the very same completions.

Additional information about the issue

No response