Apache HBase · API Governance Rules

Apache HBase API Rules

Spectral linting rules defining API design standards and conventions for Apache HBase.

14 Rules error 3 warn 9 info 2
View Rules File View on GitHub

Rule Categories

hbase no operationid path schema

Rules

error
hbase-operation-summary
All HBase REST API operations must have a summary
$.paths[*][get,put,post,delete,patch]
error
hbase-operation-id
All HBase REST API operations must have an operationId
$.paths[*][get,put,post,delete,patch]
warn
hbase-operation-tags
All HBase REST API operations must have at least one tag
$.paths[*][get,put,post,delete,patch]
warn
hbase-schema-description
All HBase schema components must have a description
$.components.schemas[*]
info
hbase-property-description
All HBase schema properties should have descriptions
$.components.schemas[*].properties[*]
warn
hbase-info-contact
API info must include contact information
$.info
warn
hbase-info-license
API info must include license information
$.info
warn
hbase-path-parameters-described
All HBase path parameters must have descriptions
$.paths[*][*].parameters[?(@.in=='path')]
error
hbase-success-response
All HBase operations must define at least one 2xx response
$.paths[*][get,put,post,delete,patch].responses
warn
path-params-casing
Path parameters should be camelCase (the dominant convention in this API).
$.paths[*].parameters[?(@.in=='path')].name
warn
operationid-casing
Operation IDs should be camelCase (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].operationId
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
info
schema-properties-casing
Schema properties should be snake_case (the dominant convention in this API).
$.components.schemas[*].properties
warn
no-empty-descriptions
Descriptions must not be empty strings.
$..description

Spectral Ruleset

Raw ↑ 
# apache-hbase — Spectral ruleset (strengthened)
# Plain Spectral. Existing hand-authored rules preserved; measured rules added
# from this provider's own OpenAPI conventions by strengthen_ruleset.py,
# then self-validated against the spec.
#
# Provenance:
#   - path-params-casing: camel @ 94% (n=18)
#   - operationid-casing: camel @ 100% (n=13)
#   - schema-names-casing: pascal @ 100% (n=8)
#   - schema-properties-casing: snake @ 36% (n=25)
#   - merge: kept 9 existing, added 5 measured, upgraded 0
#   - added: path-params-casing, operationid-casing, schema-names-casing, schema-properties-casing, no-empty-descriptions
extends:
  - spectral:oas
rules:
  hbase-operation-summary:
    description: All HBase REST API operations must have a summary
    severity: error
    given: $.paths[*][get,put,post,delete,patch]
    then:
      field: summary
      function: truthy
  hbase-operation-id:
    description: All HBase REST API operations must have an operationId
    severity: error
    given: $.paths[*][get,put,post,delete,patch]
    then:
      field: operationId
      function: truthy
  hbase-operation-tags:
    description: All HBase REST API operations must have at least one tag
    severity: warn
    given: $.paths[*][get,put,post,delete,patch]
    then:
      field: tags
      function: truthy
  hbase-schema-description:
    description: All HBase schema components must have a description
    severity: warn
    given: $.components.schemas[*]
    then:
      field: description
      function: truthy
  hbase-property-description:
    description: All HBase schema properties should have descriptions
    severity: info
    given: $.components.schemas[*].properties[*]
    then:
      field: description
      function: truthy
  hbase-info-contact:
    description: API info must include contact information
    severity: warn
    given: $.info
    then:
      field: contact
      function: truthy
  hbase-info-license:
    description: API info must include license information
    severity: warn
    given: $.info
    then:
      field: license
      function: truthy
  hbase-path-parameters-described:
    description: All HBase path parameters must have descriptions
    severity: warn
    given: $.paths[*][*].parameters[?(@.in=='path')]
    then:
      field: description
      function: truthy
  hbase-success-response:
    description: All HBase operations must define at least one 2xx response
    severity: error
    given: $.paths[*][get,put,post,delete,patch].responses
    then:
      function: schema
      functionOptions:
        schema:
          minProperties: 1
  path-params-casing:
    description: Path parameters should be camelCase (the dominant convention in this API).
    severity: warn
    given: $.paths[*].parameters[?(@.in=='path')].name
    then:
      function: casing
      functionOptions:
        type: camel
  operationid-casing:
    description: Operation IDs should be camelCase (the dominant convention in this API).
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].operationId
    then:
      function: casing
      functionOptions:
        type: camel
  schema-names-casing:
    description: Component schema names should be PascalCase (the dominant convention in this API).
    severity: warn
    given: $.components.schemas
    then:
      field: '@key'
      function: casing
      functionOptions:
        type: pascal
  schema-properties-casing:
    description: Schema properties should be snake_case (the dominant convention in this API).
    severity: info
    given: $.components.schemas[*].properties
    then:
      field: '@key'
      function: casing
      functionOptions:
        type: snake
  no-empty-descriptions:
    description: Descriptions must not be empty strings.
    severity: warn
    given: $..description
    then:
      function: truthy