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.

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

Missing HeaderLayoutType #498

Closed
Bux42 opened this issue Oct 14, 2021 · 1 comment · Fixed by #562
Closed

Missing HeaderLayoutType #498

Bux42 opened this issue Oct 14, 2021 · 1 comment · Fixed by #562
Assignees

Comments

@Bux42
Copy link

Bux42 commented Oct 14, 2021

Hello,

There are two out out of four HeaderLayoutTypes being handled in those switch statements:

"Extended" and "Minimal" (already present in HeaderLayoutTypes enum) are missing from those two switches

Could you add those?

Thanks in advance!

@jansenbe jansenbe self-assigned this Dec 2, 2021
@jansenbe
Copy link
Contributor

jansenbe commented Dec 2, 2021

Nice catch @Bux42 . I've just pushed a fix for this, please test with the next nightly and re-open the issue if the problem still persists.

@jansenbe jansenbe closed this as completed Dec 2, 2021
fzbm added a commit to fzbm/pnpframework that referenced this issue Jan 3, 2022
The previously made changes for fix pnp#498 were missing changes required
for provisioning the header information.

Additional changes:

* Removed case for "HeaderLayoutType.Standard" in "ExtractObjects",
  because "default" already handles this.
* Removed "scope" variable, because it is not used.
* Removed the "Emphasis" type reference from "Enum.TryParse", because
  the "out" variable already specifies the type.
* "ProvisionObjects" now exits as soon as possible if no changes are
  required. This also moves a possible server call for loading the web
  URL to a state, were this information would be required.
* Introduced some (single) blank lines to increase the readability of
  the code.
czullu pushed a commit to MondayCoffee/pnpframework that referenced this issue Jan 7, 2022
@czullu czullu mentioned this issue Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants