Skip to content

environmentVar could use a "unique" constraints #247

Open
#1088
Open
environmentVar could use a "unique" constraints#247
#1088
Assignees
jkowalleck
Labels
breaking-changescap: formulationCapability: Formulation
Milestone
2.0

Description

@jkowalleck
jkowalleck
opened on Jun 16, 2023
          since a var can only have exactly one value, it is desireable to have a

constraint that each var is used only once in the context of it's environmentVars container.

Originally posted by @jkowalleck in #222 (comment)

Activity

  1. jkowalleck
    added this to the 1.6 milestone on Jun 16, 2023

  2. jkowalleck commented on Dec 4, 2023

    @jkowalleck
    jkowalleck
    on Dec 4, 2023
    MemberAuthor

    I'd suggest to drop this from 1.6
    this looks like a breaking change !

  3. jkowalleck
    modified the milestones: 1.6, 2.0 on Dec 4, 2023
  4. jkowalleck
    added
    breaking-changes
    on Dec 4, 2023
  5. jkowalleck
    self-assigned this
    on Aug 24, 2026
  6. jkowalleck
    added a parent issue on Sep 10, 2026
  7. jkowalleck
    linked a pull request that will close this issueformulation environmentVars as system-independent key-value #1088on Sep 10, 2026
  8. jkowalleck
    added
    cap: formulationCapability: Formulation
    on Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

breaking-changescap: formulationCapability: Formulation

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions