Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pymemri pymemri
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 44
    • Issues 44
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MemriMemri
  • pymemripymemri
  • Issues
  • #133
Closed
Open
Issue created Apr 12, 2022 by Aglaia@RuskiBusinessOwner

Handle missing schema classes

Happens when: client gets an item from the Pod, either directly or as edge of other item

Current behaviour: If schema is defined locally (central schema or registered in PodClient), everything works If schema cannot be found, PodClient throws an error.

Desired behaviour: Needs some discussion Current behaviour is often issue when an item has an edge to another item with an unknown schema. Possible approach: have a flag in pod to ignore, throw warning, or error when encountering unknown Schema.

┆Issue is synchronized with this Clickup by Unito

Edited Apr 12, 2022 by Aglaia
Assignee
Assign to
Time tracking