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.

Sign up for GitHub

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

Jump to bottom

6/02 3:00 PM Publish #10128

Merged
merged 2 commits into from
Jun 2, 2023
Merged

6/02 3:00 PM Publish #10128

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
77b7053
Remove nonexistant history for Get-SecureRandom (#10125)
crisman Jun 2, 2023
add1340
Cmdlet now uses JsonSchema.NET (#10126)
sdwheeler Jun 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 2 additions & 10 deletions reference/7.4/Microsoft.PowerShell.Utility/Get-SecureRandom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ Name Count

### Example 11: Use the Count parameter

You can now use the **Count** parameter without piping objects to `Get-SecureRandom`. The following
You can use the **Count** parameter without piping objects to `Get-SecureRandom`. The following
example gets three random numbers less than 10.

```powershell
Expand Down Expand Up @@ -236,7 +236,7 @@ from the collection up to the number specified by **Count**. Enter the objects,
contains the objects, or a command or expression that gets the objects. You can also pipe a
collection of objects to `Get-SecureRandom`.

Beginning in PowerShell 7, the **InputObject** parameter accepts arrays that can contain an empty
The **InputObject** parameter accepts arrays that can contain an empty
string or `$null`. The array can be sent down the pipeline or as an **InputObject** parameter value.

```yaml
Expand Down Expand Up @@ -361,14 +361,6 @@ shows the output type for each of the numeric input types.
| Double | Double |
| Single | Double |

Beginning in Windows PowerShell 3.0, `Get-SecureRandom` supports 64-bit integers. In Windows
PowerShell 2.0, all values are cast to **System.Int32**.

Beginning in PowerShell 7, the **InputObject** parameter in the **RandomListItemParameterSet**
parameter set accepts arrays that contain an empty string or `$null`. In earlier PowerShell
versions, only the **Maximum** parameter in the **RandomNumberParameterSet** parameter set accepted
an empty string or `$null`.

## RELATED LINKS

[Get-Random](Get-Random.md)
18 changes: 11 additions & 7 deletions reference/7.4/Microsoft.PowerShell.Utility/Test-Json.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml
Locale: en-US
Module Name: Microsoft.PowerShell.Utility
ms.date: 03/14/2023
ms.date: 06/02/2023
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/test-json?view=powershell-7.4&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Test-Json
Expand Down Expand Up @@ -334,14 +334,18 @@ This cmdlet returns `$true` if the JSON is valid and otherwise `$false`.

## NOTES

The `Test-Json` cmdlet is implemented using the
[NJsonSchema Class](https://github.com/RSuter/NJsonSchema).

Since PowerShell 6, PowerShell uses the Newtonsoft.Json assemblies for all JSON functions.
Newtonsoft's implementation includes several extensions to the JSON standard, such as support for
comments and use of single quotes. For a full list of features, see the Newtonsoft documentation at
Since PowerShell 6, PowerShell uses the Newtonsoft.Json assemblies for JSON functions. Newtonsoft's
implementation includes several extensions to the JSON standard, such as support for comments and
use of single quotes. For a full list of features, see the Newtonsoft documentation at
[https://www.newtonsoft.com/json](https://www.newtonsoft.com/json).

Beginning in PowerShell 7.4, `Test-Json` uses
[JsonSchema.NET](https://www.nuget.org/packages/JsonSchema.Net) for schema validation. With this
change, `Test-Json` no longer supports Draft 4 schemas. For more information about JSON schema
specifications, see the documentation at
[JSON-Schema.org](https://json-schema.org/specification.html).


## RELATED LINKS

[An Introduction to JavaScript Object Notation (JSON) in JavaScript and .NET](/previous-versions/dotnet/articles/bb299886(v=msdn.10))
Expand Down