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 221
    • Issues 221
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • Merge requests
  • !483

Introducing parser levels, defining the order of processing

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged David Sikter requested to merge add-parser-levels into v1.0.0 Dec 14, 2021
  • Overview 3
  • Commits 4
  • Pipelines 4
  • Changes 6

Parser can define a field level which determines which order they will be run in, as requested by #668 (closed) . The default value is 0. Level 0 parsers are run first, then level 1, then level 2, and so on. The code defined in Upload and Calc for special handling of the phonopy parser is therefore also removed (the functionality defined there should be moved to the parser instead).

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: add-parser-levels