Skip to content

Bug report: Issues with number parameters validation #6211

@mkm17

Description

@mkm17

Priority

(Low) Something is a little off

Description

Hi, I have observed a strange issue with number parameters. While making some changes for the page section add command, everything was ok with CLI version 7.10.0. However, when I rebased the main branch to version 8.1.0, I saw the following messages, indicating that the number passed no longer meets the Number.isInteger(args.options.order) condition. Do you see the same effect?

image

Steps to reproduce

  • Get the newest version of CLI
  • run the command with number parameter like m365 spo page text add --pageName Test2.aspx --webUrl https://tenant.sharepoint.com/sites/AudienceTest --section 1 --text "text" or
  • run the command m365 spo page section add --pageName Test2.aspx --webUrl https://mknetpl.sharepoint.com/sites/AudienceTest --sectionTemplate TwoColumn --order 1

Expected results

The number parameter should pass the validation.

Actual results

The number parameter does not pass the Number.isInteger(x) validation.

Diagnostics

No response

CLI for Microsoft 365 version

8.1.0

nodejs version

v20.11.0

Operating system (environment)

Windows

Shell

PowerShell

cli doctor

No response

Additional Info

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions