Consider merged/overridden files in Compose

Open
#158 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 with the linked Compose documentation on merging multiple files, then review the language server's Compose features and their assumptions about file isolation. The issue names no files, tests, or entry points; first identify the affected areas and define expected behavior for merged and overridden files.

Written by the indexing model from the issue text.

Description

compose

Compose will merge files to try and reconcile attributes that have been defined multiple times. We will need to review this behaviour to understand what implications it may have on the various features given that the language server is currently developed under the assumption that every file is (for the most part) in complete isolation of each other.

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.