Sp-dev-docs: debugLocale not allowed

[JBorras-summar]

When setting "debugLocale" in manifest.json compiler says it's not allowed

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 33394188-10be-0875-025d-9ffff6618df9
• Version Independent ID: ca9875f8-4f6a-21d3-8483-66ced7c2d55c
• Content: Localize SharePoint Framework client-side web parts
• Content Source: docs/spfx/web-parts/guidance/localize-web-parts.md
• Product: sharepoint
• Technology: sharepoint-framework
• GitHub Login: @spdevdocs
• Microsoft Alias: spdevdocs

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[andrewconnell]

Not sure why that's in the docs as that's not a valid option on the write-manifest.json file (look at the schema linked in the file for everything that is allowed).

To test, specify the locale to serve upon the local workbench like this:

gulp serve --locale=fr-ca

Will get this fixed in the docs...

[cwdata]

@andrewconnell,
AFAIK the locale option on the command line doesn't work either. You now have to use buildSingleLocale in the write-manifest.json. For reference see issue #3248.

[andrewconnell]

@cwdata said:

AFAIK the locale option on the command line doesn't work either

It does work... I tested it before I wrote the above comment.

As for the buildSingleLocale, yes that is an option within the write-manifest.json file if you want to limit the bundle creation to a specific locale. That's useful for packaging, but in testing, it has zero use as it's only used when bundling with the --ship or -p flag.

[bcameron1231]

@andrewconnell So can there be an action item to fix the documentation to remove debugLocale or update the documentation for clarity on the newer versions of SPFx that no longer support it? I had commented on the other linked document, just to confirm what the communication of this change should be for the localize-web-part documentation.

[andrewconnell]

@bcameron1231 Correct... this is a doc bug. That's why I flagged this issue as a bug & assigned it to me to get fixed.

[bcameron1231]

Ah, I missed that :)

Thanks!!

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues