The link in README.md points to https://developer.microsoft.com/json-schemas/ but that's a 404

Newly added elements for Viva Connections dashboard card support have duplicate descriptions. Maybe a copypaste error?

"dashboardCardIcon": {
            "type": "object",
            "description": "Represents a configuration for the source of the card’s content",

          ...
        "dashboardCardContentSource": {
            "type": "object",
            "description": "Represents a configuration for the source of the card’s content.",

Suggested description for dashboardCardIcon: Defines the icon properties of a given dashboard card.

https://developer.microsoft.com/json-schemas/ leads to 404 error

Seems to be an unneeded comma on line 139.

`Parse error on line 139:
... },

-----------------------^
Expecting 'STRING', got '}'`

I came across this Office doc , it mentioned the repeat json metadata for excel custom function , which I can't find in custom-functions.schema.json ，may be it should be updated?

The 'setSiteBranding' verb has a 'headerLayout' property, however the schema for this property only allows for 2 of the 4 options for this configuration. "Standard" and "Compact" are supported in SharePoint, however "Minimal" and "Extended" are both not allowed in the schema.

(line 1043 of this schema JSON) https://github.com/microsoft/json-schemas/blob/main/sp/site-design-script-actions.schema.json

Hi,

We have been trying to update Appear as, Solution type and Legal of a SPFx solution without any success. Can you please help me identify which of the properties in this schema https://github.com/microsoft/json-schemas/blob/main/spfx-build/package-solution.schema.json#L45 are connected to those given properties?

Thank you in advance for your help.

Kind regards,
Anisia Pop

VSCode includes many config files (e.g., .vscode/settings.json, .vscode/extensions.json, .vscode/tasks.json, .vscode/launch.json) with unspecified schemas. Refer to the default VSCode settings.

It would be ideal to write draft v4 JSON schemas for all of these files as recommended by JSON Schema Store for maximum compatibility with existing tools. Offering a schema makes it easy for projects that desire to validate their workspace config files in CI to do so with minimal effort.

Question (the more details, the better)

I´ve very annoyed that json doenst support comments inside code -.-

I´ve read that the Json Version 5 will support comments inside the code.

Is there any plan to add Json5 Support for the json schema?

https://json5.org/

hey @shagra-ms do you have an idea why i cant use the openContextMenu customRowAction from the v2 sp-formatting schema?

i try this:
{ "elmType": "button", "customRowAction": { "action": "openContextMenu" }, "txtContent": "Kontextmenü", "attributes": { "class": "sp-row-button ms-bgColor-neutralLighter ms-fontWeight-semibold" }, "style": { "width": "145px", "height": "48px", "margin": "20px 0 10px 0" } }

but nothing happens when i click on the button.

I didnt find any sample in the docs for that, only for setValue and that works great

The problem

We recently merged an update in PR #115, which can be seen here:

main branch:

live branch:

However 24 hours later, the CDN deployed file is still missing the new choiceList item:
https://developer.microsoft.com/json-schemas/rush/v5/command-line.schema.json

Possible regression?

@DevArvindsa Maybe the json-schemas deployment was broken by your recent change in 04df543 ? Could someone from Microsoft investigate? Thanks!

CC @iclanton @apostolisms @EscapeB

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Dev preview schema missing “type”: "object" for the following properties:

https://ajv.js.org/strict-mode.html#require-applicable-types

Category

• Bug

Describe the bug

This is a duplicate issue of #5361.

Some Site Script examples in the latest documentation for Site design JSON schema fail to validate against the latest Site Script Schema.

Certain Site Script examples do validate (with some modifications to the JSON site script as noted in "N.B." below). I can provide examples of those if needed.

I might have tracked the issue to the way the "additionalProperties" property is specified in several action definitions, but I need confirmation in case the validation error lies elsewhere.

Steps to reproduce

1. Use the example JSON in the Define a new content type section of the documentation to form a site script. For reference, the following is a site script constructed in this way:

{ "$schema": "schema.json", "actions": [ { "verb": "createContentType", "name": "Contoso Projects", "description": "custom list content type", "parentName": "Item", "hidden": false, "subactions": [ { "verb": "addSiteColumn", "internalName": "siteColumn1Text" }, { "verb": "addSiteColumn", "internalName": "siteColumn2Number" }, { "verb": "addSiteColumn", "internalName": "siteColumn3Note" } ] } ] }

N.B. While the documentation specifies it, I have removed the following properties from this Site Script: "bindingdata" and "version". When these properties are included, the Site Script JSON will always fail to validate against the latest Site Script Schema, because there is an "additionalProperties" property that prohibits them—please refer to the Site Script Schema for confirmation. In the previous (draft-06) Site Script Schema, those properties were defined and allowed.

2. Use a JSON Schema validator to validate the JSON above against the latest Site Script Schema. E.g. I have used JSON Schema Validator as well as Ajv to confirm the invalidity.

3. See validation error.

Expected behavior

JSON Site Script example should be valid against latest Site Script Schema.

Additional context

The main validation issue seems to be that the Site Script action has properties the schema does not allow. However, the errors seem to suggest that none of the properties are allowed by the Site Script Schema, even the required ones for this example (e.g. verb, name, hidden).

This suggests that the error is in how the "additionalProperties" property is set in the Site Script Schema for the action. I can provide additional information on this if needed.

Hey @shagra-ms when would the new schema-update available over https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json ?

It's avery interessting update ;-)

Im unsure where to give information about this bug, whether it is an documentation error or teams-api error.

In the V1.16 schema for TeamsApps teams/v1.16/MicrosoftTeams.schema.json there is the version described as:

 "version": {
      "type": "string",
      "description": "The version of the app. Changes to your manifest should cause a version change. This version string must follow the semver standard (http://semver.org).",
      "maxLength": 256
    },

On http://semver.org the version can be:

<valid semver> ::= <version core>
                 | <version core> "-" <pre-release>
                 | <version core> "+" <build>
                 | <version core> "-" <pre-release> "+" <build>

<version core> ::= <major> "." <minor> "." <patch>
<build> ::= <dot-separated build identifiers>
// removed for brevity

-> So the version "version": "1.0.0+20240226" should be valid.
With "manifestVersion": "1.15", this works as expected.
But with "manifestVersion": "1.16", we get an error from the admin Teams UI "Upload a custom app" (Post https://graph.microsoft.com/beta/appCatalogs/teamsApps) results in 400 error.

{
    "error": {
        "code": "BadRequest",
        "message": "App version supports only numbers in the '#.#.#' format.",
        "innerError": {
            "code": "UnableToParseTeamsAppManifest",
            "message": "App version supports only numbers in the '#.#.#' format.",
            "details": [
                {
                    "code": "VersionContainsOnlyNumbersDotSeparated",
                    "message": "App version supports only numbers in the '#.#.#' format."
                }
            ],
            "date": "2024-02-26T15:52:35",
            "request-id": "d65a27a7-84d7-4d31-b080-5d589b692a8b",
            "client-request-id": "d65a27a7-84d7-4d31-b080-5d589b692a8b"
        }
    }
}

I am trying to extract the custom SharePoint group using the extract configuration schema method. Here is the configuration settings I did.

MySchema.Json Xml File Contents

{ "$schema":"https://aka.ms/sppnp-extract-configuration-schema", "persistAssetFiles": true, "handlers": [ "Lists", "WebSettings", "Pages" ], "pages": { "includeAllClientSidePages": true }, "siteSecurity": { "includeSiteGroups": true } }

Get-PnPSiteTemplate -out testtest.xml -Configuration MySchema.json

Somehow testtest.xml file not returning any SharePoint group that I created. Any idea of how can be achieved using configuration schema.

Error observed when uploading: defaultGroupCapability.groupChat | Property "groupChat" has not been defined and the schema does not allow additional properties.

Issue: note the schema uses groupchat, and docs have it camel cased: https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema

It appears this is in the 1.16 schema, too. Looking through the schema, a user can provide groupchat OR groupChat and it will resolve in most cases. However, in the case of the specific property defaultGroupCapability, it does not.

Possibly related to #116.

enumMemberOrder was added to api-extractor/v7/api-extractor.schema.json in September 2022 (see 52c734d), but it doesn't appear in https://developer.microsoft.com/json-schemas/api-extractor/v7/api-extractor.schema.json.