[typespec-vscode] setting custom entrypoint file for tsp project

[mzhongl524]

Fix: #6062

Setting custom entrypoint file for tsp project

[github-actions]

All changed packages have been documented.

• ✅ @typespec/compiler
• ✅ typespec-vscode

Show changes

@typespec/compiler - feature [✏️](https://github.com/mzhongl524/typespec/edit/custom-entrypoint-file-for-tsp-project/.chronus/changes/custom-entrypoint-file-for-tsp-project-2025-6-24-6-57-40 copy.md?pr=//pull/7929)

[LSP] Allow configuring which file names to use as entrypoints

typespec-vscode - feature ✏️

Allow configuring which file names to use as entrypoints

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[timotheeguerin]

@mzhongl524 pleas try to submit the PR as a draft(Dropdown on the create Pr button) not converting it to a draft otherwise it still request review from everybody immediately.

[timotheeguerin]

file name is inconsistent with the file name its testing

[timotheeguerin]

remove top level describe

[timotheeguerin]

I thought we agreed that this should be deleted and entrpoints should just default to main.tsp above with the package.json being the outerbound regardless

[RodgeFu]

yeah, we did that change but then realize it breaks the behavior that if user sets nothing but have main defined in package.json instead, it should have higher priority than main.tsp file. so made some change there. thanks.

[timotheeguerin]

Which does seem expected to me. Can you show a file structure where you think the user wouldn't want that?

[RodgeFu]

something like below. the entrypoint should be resolved as 'abc.tsp' instead of 'main.tsp' if user doesn't set the entrypoint explicitly in vscode.

-- main.tsp
 - abc.tsp
 - package.json <-- in the package.json, set the main to 'abc.tsp'

[timotheeguerin]

Here I would expect abc to be the entrypoint. The package.json marks the boundary anyway where packages are installed. They main.tsp most likely is not working.
Package.json is the closest we currently have to make something as a project

[RodgeFu]

yes, so we need to check the "main.tsp" after the package.json part when the entrypoints are not set explicitly, otherwise if we default to ["main.tsp"] and search for it before the package.json part, the "main.tsp" will be returned (line 34 above) instead of the "abc.tsp".

[timotheeguerin]

Doesn't that just work if the algorithm is

while dir:
If has tsp main in package.json
Return
If has file in entrypoints(default to main.tsp)
Return
Dir = parent dir

[RodgeFu]

But I think if user set the entrypoints in the vscode settings explicitly, it should have higher priority than the tsp main in package.json, so the priority is like

1. explicit settings of entrypoint
2. tsp main in package.json
3. default 'main.tsp' (when nothing set above)

[timotheeguerin]

I disagree. If you hit this as said above it most likely will break as dependencies are below.
Packagejson mark the package boundary it doesn't make sense imo it would work outside of it

[RodgeFu]

Do you mean the search should stop at the package.json level? I agree with that. The pri i mentioned above is in the same dir level, it's something like below in my mind:

while(valid dir || no package.json)
{
check entrypoints explicitly set, return if found
check tsp main in package.json, return if found
check default 'main.tsp' if entrypoints not set explicitly, if found, save as potential entrypoint to be returned
dir = parent dir
}