Skip to content

Introduce CI stage for REST Spec, related to #158

Lucca Jimenez Könings requested to merge istlujime/go-sdn:develop into develop

Attention: This will instantly break the CI if merged, as the corresponding file to be linted is not yet on master or develop

This introduces a CI stage for #158 (closed) . The linter used is the ibm-openapi-validator, which is node.js based.

Description

Related Issue

#158 (closed)

Motivation and Context

This adds a linter for our REST spec, to avoid errors and improve code quality. This enables us to spend less time on fixing bugs and more time on implementing features.

How Has This Been Tested?

I ran this in my private CI playground and it worked. I cannot test it on goSDN/develop or goSDN/master, since these environments use custom runners. Additionally, the rest spec has not yet been pushed to develop or master. Testing is difficult.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation. Maybe not docs, but contributors guidelines
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Merge request reports