mirror of https://github.com/docker/compose.git
950577d60f
We want to give feedback to the user as soon as possible about the validity of the config supplied for the services. When extending a service, we can validate that the fields are correct against our schema but we must wait until the *end* of the extends cycle once all of the extended dicts have been merged into the service dict, to perform the final validation check on the config to ensure it is a complete valid service. Doing this before that had happened resulted in false reports of invalid config, as common config when split out, by itself, is not a valid service but *is* valid config to be included. Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com> |
||
|---|---|---|
| .. | ||
| circle-1.yml | ||
| circle-2.yml | ||
| common.yml | ||
| docker-compose.yml | ||
| invalid-links.yml | ||
| invalid-net.yml | ||
| invalid-volumes.yml | ||
| nested-intermediate.yml | ||
| nested.yml | ||
| no-file-specified.yml | ||
| nonexistent-path-base.yml | ||
| nonexistent-path-child.yml | ||
| nonexistent-service.yml | ||
| service-with-invalid-schema.yml | ||
| service-with-valid-composite-extends.yml | ||
| specify-file-as-self.yml | ||
| valid-common-config.yml | ||
| valid-common.yml | ||
| valid-composite-extends.yml | ||
| valid-interpolation-2.yml | ||
| valid-interpolation.yml | ||