Skip to content

Configuration group naming conventions and adjustments #271

@samdark

Description

@samdark

ℹ️ Note that this is not about configuration file names. It is about config groups.

Problem

  • Names do not show what is container config and what are params.
  • There is no naming convention defined.

Solution

  1. Accept/merge "022 - Config groups":
  1. Adjust runners:
  1. Adapt packages to new runners
  1. Adjust group names in existing packages providing configs:
  • commondi
  • webdi-web
  • consoledi-console
  • providers → di-providers
  • providers-web → di-providers-web
  • providers-consoledi-providers-console
  • delegatesdi-delegates
  • delegates-webdi-delegates-web
  • delegates-consoledi-delegates-console
  • tagsdi-tags
  • tags-webdi-tags-web
  • tags-console → di-tags-console

4.1. Create and merge adapt PRs in released packages:

4.2. Create and merge adapt PRs in non-released packages:

4.3. Make releases:

  1. Adapt application templates:
  1. Adapt demo:
  1. Write down short upgrade guides and publish to chats.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions