Bump prettier from 2.8.1 to 2.8.8

[dependabot[bot]]

Bumps prettier from 2.8.1 to 2.8.8.

Release notes

Sourced from prettier's releases.

2.8.8

This version is a republished version of v2.8.7. A bad version was accidentally published and it can't be unpublished, apologies for the churn.

2.8.7

• Allow multiple decorators on same getter/setter

🔗 Changelog

2.8.6

• Allow decorators on private members and class expressions

🔗 Changelog

2.8.5

• Support TypeScript 5.0

🔗 Changelog

2.8.4

🔗 Changelog

2.8.3

Support Angular 15.1

🔗 Changelog

2.8.2

🔗 Changelog

Changelog

Sourced from prettier's changelog.

2.8.8

This version is a republished version of v2.8.7. A bad version was accidentally published and it can't be unpublished, apologies for the churn.

2.8.7

diff

Allow multiple decorators on same getter/setter (#14584 by @​fisker)

// Input
class A {
  @decorator()
  get foo () {}
@​decorator()
set foo (value) {}
}
// Prettier 2.8.6
SyntaxError: Decorators cannot be applied to multiple get/set accessors of the same name. (5:3)
3 |   get foo () {}
4 |

> 5 |   @​decorator()
|   ^^^^^^^^^^^^
6 |   set foo (value) {}
7 | }
// Prettier 2.8.7
class A {
@​decorator()
get foo() {}
@​decorator()
set foo(value) {}
}

2.8.6

diff

Allow decorators on private members and class expressions (#14548 by @​fisker)

// Input
</tr></table> 

... (truncated)

Commits

• 1b7fad5 Release 2.8.8
• 543a9d7 Release 2.8.7
• f9fae7f Allow multiple decorators on same getter/setter (#14584)
• 10fe1ed Release 2.8.6
• 44aef0b Allow decorator on private members and class expressions (#14548)
• ddf3b43 Clean changelog
• 71ba29f Git blame ignore 2.8.5
• c1808e8 Bump Prettier dependency to 2.8.5
• 0a79535 Release 2.8.5
• 019ebe5 Support TypeScript 5 (backport #14391 and #13819) (#14512)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[giufus]

Interesting project @Zavy86

@Wabuo It can't be considered a fix, is a customisation and customisations are git-ignored. Add a custom style like this.

1. Locate the Custom CSS File: Find or create the styles/styles-custom.css file in your WikiDocs installation.
   This ensures your changes won't be overwritten by future updates.

2. Add the Following CSS Rule:

/* Prevent title wrapping and add ellipsis if it overflows */
#logo-container h1 {
    white-space: nowrap;     /* Prevent the text from wrapping to a new line */
    overflow: hidden;        /* Hide the part of the text that overflows */
    text-overflow: ellipsis; /* Show an ellipsis (...) to indicate hidden text */
    
    /* Optional: You might slightly reduce the default size to give more room */
    /* Experiment with values like 3.2rem or 3rem if needed */
    font-size: 3.2rem;
}

[Zavy86]

Thanks @giufus, do you think it can be applied to standard css or is it better to keep it only as custom?

[giufus]

Hi @Zavy86 I'm not a CSS or accessibility expert, so I don't want to steer you in the wrong direction. My opinion is that custom css is a valid option, but if you like the suggested style, applying it as default in the #logo-container is a good idea. I especially liked the text-overflow: ellipsis; that I did not know before.

[Zavy86]

feel free to make a pull requests ;-)