Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M MEC Robot Test Suite
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MEC - Multi-access Edge ComputingMEC - Multi-access Edge Computing
  • MEC Robot Test Suite
  • Issues
  • #38
Closed
Open
Issue created Feb 15, 2021 by Simon Pastor@pastorsDeveloper

Plugtest 2021: Specification discussion: non existent attribute in a json body should be ignored

Used as a placeholder for the specific issue below:

When receiving a json body and an attribute is not defined, the current expectation from the plugtest is to receive a code 400. Is a more appropriate action to ignore the unknown parameter? This allows a less strict approach. It was not found in the spec what should be the behavior as a result of this situation. Need a clearer spec indication in order to standardized the implementations.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking