Consider OCI artifacts and Git references when including other Compose files

Open
#159 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker-compose, go
Domain
devtools

Research direction

Start by reviewing the language server's existing handling of included Compose files and the features it exposes. Assess OCI-artifact and Git-file references and their implications; the issue does not name files, tests, or a specific completion condition, so the needed scope must first be defined.

Written by the indexing model from the issue text.

Description

compose

Compose supports including Compose files as OCI artifacts or files that are in Git. We should review this use case and its implications on the features being offered in the language server.

Dominant language
Go
Stars
185
Forks
28
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/docker-language-server

All issues in docker/docker-language-server

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.