Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 215
    • Issues 215
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #519
Closed
Open
Issue created Mar 29, 2021 by Lauri Himanen@himanel1Maintainer

FastAPI reference resolution

The current mechanism for resolving references through FastAPI is inconvenient/not fully functional.

I guess there are at least three different scenarios for resolving references:

  1. Do not resolve, just keep the reference as a string.
  2. Place the referenced section/quantity in the returned archive in its correct location (useful for deserializing python metainfo objects).
  3. Resolve the reference in place (useful for environments where the python metainfo package is not available, e.g. in the GUI).

Maybe there could be an API parameter that determines the resolution mechanism? The implementation should also be able to resolve the newly added quantity references and lists of references.

Assignee
Assign to
Time tracking