Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix network role mapping #93

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Fix network role mapping

92010cc
Select commit
Loading
Failed to load commit list.
Open

Fix network role mapping #93

Fix network role mapping
92010cc
Select commit
Loading
Failed to load commit list.
HM Linter / hmlinter failed Jan 15, 2025 in 1m 56s

hmlinter checks failed

61 errors

Request details

  • GitHub Event ID: 764e8b30-d32e-11ef-98a3-79c1f67baaea
  • API Gateway ID: f3ef3576-1cdc-4bf6-8147-208d796fa200
  • Lambda ID: 14311f9b-69a8-4999-b1ac-1ad9a84449e5
  • Log Stream: 2025/01/15/[$LATEST]6c4f3b7453da4385bb4ea8b4b7f5a4db

Annotations

Check failure on line 228 in inc/class-response-command.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/class-response-command.php#L228

Object property "$formatOutput" is not in valid snake_case format, try "$format_output"
Raw output
{
  "line": 228,
  "column": 20,
  "severity": "error",
  "message": "Object property \"$formatOutput\" is not in valid snake_case format, try \"$format_output\"",
  "source": "WordPress.NamingConventions.ValidVariableName.UsedPropertyNotSnakeCase"
}

Check failure on line 229 in inc/class-response-command.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/class-response-command.php#L229

Object property "$preserveWhiteSpace" is not in valid snake_case format, try "$preserve_white_space"
Raw output
{
  "line": 229,
  "column": 20,
  "severity": "error",
  "message": "Object property \"$preserveWhiteSpace\" is not in valid snake_case format, try \"$preserve_white_space\"",
  "source": "WordPress.NamingConventions.ValidVariableName.UsedPropertyNotSnakeCase"
}

Check failure on line 1 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L1

Missing file doc comment
Raw output
{
  "line": 1,
  "column": 1,
  "severity": "error",
  "message": "Missing file doc comment",
  "source": "Squiz.Commenting.FileComment.Missing"
}

Check failure on line 34 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L34

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 34,
  "column": 5,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 98 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L98

Missing parameter comment
Raw output
{
  "line": 98,
  "column": 4,
  "severity": "error",
  "message": "Missing parameter comment",
  "source": "Squiz.Commenting.FunctionComment.MissingParamComment"
}

Check failure on line 143 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L143

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 143,
  "column": 5,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 163 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L163

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 163,
  "column": 5,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 332 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L332

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 332,
  "column": 45,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 333 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L333

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 333,
  "column": 106,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 336 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L336

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 336,
  "column": 43,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 337 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L337

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 337,
  "column": 75,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 339 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L339

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 339,
  "column": 44,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 342 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L342

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 342,
  "column": 45,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 343 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L343

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 343,
  "column": 98,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 346 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L346

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 346,
  "column": 53,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 347 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L347

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 347,
  "column": 122,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 350 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L350

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 350,
  "column": 55,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 351 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L351

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 351,
  "column": 126,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 354 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L354

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 354,
  "column": 50,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 355 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L355

Detected usage of a non-sanitized input variable: $_POST['sso_idp_metadata']
Raw output
{
  "line": 355,
  "column": 61,
  "severity": "error",
  "message": "Detected usage of a non-sanitized input variable: $_POST['sso_idp_metadata']",
  "source": "HM.Security.ValidatedSanitizedInput.InputNotSanitized"
}

Check failure on line 355 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L355

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 355,
  "column": 93,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 368 in inc/admin/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/admin/namespace.php#L368

Detected usage of a non-sanitized input variable: $_COOKIE['sso_debug']
Raw output
{
  "line": 368,
  "column": 42,
  "severity": "error",
  "message": "Detected usage of a non-sanitized input variable: $_COOKIE['sso_debug']",
  "source": "HM.Security.ValidatedSanitizedInput.InputNotSanitized"
}

Check failure on line 2 in inc/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/namespace.php#L2

You must use "/**" style comments for a file comment
Raw output
{
  "line": 2,
  "column": 1,
  "severity": "error",
  "message": "You must use \"/**\" style comments for a file comment",
  "source": "Squiz.Commenting.FileComment.WrongStyle"
}

Check failure on line 60 in inc/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/namespace.php#L60

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 60,
  "column": 5,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}

Check failure on line 74 in inc/namespace.php

See this annotation in the file changed.

@hm-linter hm-linter / hmlinter

inc/namespace.php#L74

Inline comments must end in full-stops, exclamation marks, or question marks
Raw output
{
  "line": 74,
  "column": 5,
  "severity": "error",
  "message": "Inline comments must end in full-stops, exclamation marks, or question marks",
  "source": "Squiz.Commenting.InlineComment.InvalidEndChar"
}