Skip to content

Fix documentation compliance issues being overly stringent #491

Description

@IsakNaslundBh

Description:

https://github.com/BHoM/BHoM_Engine/pull/3438/checks?check_run_id=34182023890

Checks raised as errors here should not be errors.

  1. Descriptions should not be forced as errors on methods in the unit-test folder
  2. "input order should match input attribute order" should be a warning, not error.

Steps to reproduce:

https://github.com/BHoM/BHoM_Engine/pull/3438/checks?check_run_id=34182023890

Expected behaviour:

For both of the above errors to be downgraded to warning

Test file(s):

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

type:bugError or unexpected behaviour

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions