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

Introduce a concept of project solutions #82

Closed
alexrp opened this issue May 7, 2023 · 0 comments
Closed

Introduce a concept of project solutions #82

alexrp opened this issue May 7, 2023 · 0 comments
Labels
area: tooling Issues related to the tooling layer. type: feature Issues that are classified as feature requests.
Milestone

Comments

@alexrp
Copy link
Sponsor Member

alexrp commented May 7, 2023

Basically a celerity.solution.json looking something like this:

{
  "projects": [
    "src/project-a",
    "src/project-b"
  ]
}

This file will indicate to various tooling (e.g. the language server) which celerity.json project files (#30) should actually be loaded as user projects. Without this mechanism, we have no good way to tell if a project file is only present because it comes from a git submodule-based dependency.

@alexrp alexrp added state: approved Feature requests and housekeeping tasks that have been approved. type: feature Issues that are classified as feature requests. area: tooling Issues related to the tooling layer. labels May 7, 2023
@alexrp alexrp added this to the v1.0 milestone May 7, 2023
@alexrp alexrp self-assigned this May 7, 2023
@alexrp alexrp mentioned this issue May 7, 2023
1 task
@alexrp alexrp removed the state: approved Feature requests and housekeeping tasks that have been approved. label May 19, 2023
@alexrp alexrp closed this as completed in c26c8ac May 19, 2023
@alexrp alexrp removed their assignment Jan 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: tooling Issues related to the tooling layer. type: feature Issues that are classified as feature requests.
Development

No branches or pull requests

1 participant