Feature request: Allow to choose the SupportedUILanguages that we want to export during GetProvisioningTemplate
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 259
- Forks
- 161
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 1
Description
There is an open issue in the archived repository that was talking about the same thing...
https://github.com/pnp/PnP-Sites-Core/issues/1573
The problem is that we want to get the template of a site with some languages and resources, but we don't want to get the 51 supported by SP, only those that we are supporting, f.i. english, french, spanish, ...
Right now, we are able to set BaseTemplate to null, forcing to export all languages and resources, but it would be nice to be able to indicate somehow what languages we want to get.
Maybe something like this could work.
Also we should change this class
https://github.com/pnp/pnpframework/blob/dev/src/lib/PnP.Framework/Provisioning/ObjectHandlers/ObjectSupportedUILanguages.cs
Is this a valid approach?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing GetProvisioningTemplate behavior and src/lib/PnP.Framework/Provisioning/ObjectHandlers/ObjectSupportedUILanguages.cs, along with the related archived issue #1573. Determine how a caller could specify the supported UI languages without exporting all 51 languages; done means the template contains only the selected languages and resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100