Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Improvement]: Improve the ProjectPaths APIs to support tooling-related files #43537

Open
azinneera opened this issue Oct 31, 2024 · 0 comments
Assignees
Labels
Area/ProjectAPI Priority/High Team/DevTools Ballerina Developer Tooling ( CLI, Test FW, Package Management, OpenAPI, APIDocs ) Type/Improvement

Comments

@azinneera
Copy link
Contributor

Description

The current APIs in ProjectPaths only identify files/directories in two ways: standalone source files or files/directories that belong to a package. With tooling support, there can be files that are not a source file of a package but from the user's perspective, the file belongs to the package. This is not considered in the APIs in the ProjectPaths and therefore, causes failures in debugging in certain cases.

Therefore, these APIs need to be improved to support files related to tooling that we may introduce in the future as well.

Describe your problem(s)

No response

Describe your solution(s)

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/ProjectAPI Priority/High Team/DevTools Ballerina Developer Tooling ( CLI, Test FW, Package Management, OpenAPI, APIDocs ) Type/Improvement
Projects
None yet
Development

No branches or pull requests

1 participant