Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
M mom-ca
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 407
    • Issues 407
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Administrator
  • mom-ca
  • Issues
  • #778

Closed
Open
Created Jun 21, 2018 by Administrator@rootMaintainer

hooked-in-charter linking to a source charter not existing (anymore) creates an error

Created by: GVogeler

The actual cardinality for parameter 1 does not match the cardinality declared in the function's signature: charter:linked-fond-base-collection($entry as element()) item()*. Expected cardinality: exactly one, got 0. [at line 161, column 26, source: String]
In function:
	charter:linked-fond-base-collection(element())

We cannot control all dependencies when changing public charters, thus this kind of error could be displayed more user friendly.

Assignee
Assign to
charters hooked in into user collections
Milestone
charters hooked in into user collections
Assign milestone
Time tracking