Skip to content

feat: update prettier#535

Open
Harpush wants to merge 1 commit intoangular-split:mainfrom
Harpush:update-prettier
Open

feat: update prettier#535
Harpush wants to merge 1 commit intoangular-split:mainfrom
Harpush:update-prettier

Conversation

@Harpush
Copy link
Copy Markdown
Collaborator

@Harpush Harpush commented Apr 2, 2026

No description provided.

@Harpush Harpush requested review from Jefiozie and SanderElias April 2, 2026 12:42
@Harpush
Copy link
Copy Markdown
Collaborator Author

Harpush commented Apr 2, 2026

@Jefiozie @SanderElias Maybe it is time to change the prettier configuration?
For example semi: false to true.
What do you think?

Copy link
Copy Markdown
Contributor

@SanderElias SanderElias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with this PR, but please update the description a bit, so we can address it properly when merging.

if (logsEl.nativeElement.scroll) {
(<HTMLElement>logsEl.nativeElement).scroll({ top: this.logMessages.length * 30 })
const element = logsEl.nativeElement as HTMLElement
element.scroll({ top: this.logMessages.length * 30 })
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like it, but it doesn't have to do with prettier? Perhaps update the pr description for the other things.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Due to semi false prettier adds with the previous way a ; at the beginning which is then marked by eslint.
The solution is either to separate like I did here or change semi to true

if (logsEl.nativeElement.scroll) {
(<HTMLElement>logsEl.nativeElement).scroll({ top: this.logMessages.length * 30 })
const element = logsEl.nativeElement as HTMLElement
element.scroll({ top: this.logMessages.length * 30 })
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.
I don't mind those better typings, but it is very drive-by

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository’s formatting toolchain by bumping Prettier and applying the resulting formatting changes across a few TS/HTML/YAML/MD files.

Changes:

  • Bump prettier from ^3.0.2 to ^3.8.1 and update package-lock.json accordingly.
  • Add an npm script (prettier) and apply Prettier-driven formatting updates (TS casting style, Angular template trailing comma, YAML indentation/quoting, MD whitespace).

Reviewed changes

Copilot reviewed 6 out of 8 changed files in this pull request and generated no comments.

Show a summary per file
File Description
src/app/examples/split-transitions/split-transitions.component.ts Refactors type casting for nativeElement to align with updated formatting output.
src/app/examples/gutter-click-roll-unroll/gutter-click-roll-unroll.component.ts Same casting refactor for log auto-scroll code.
projects/angular-split/src/lib/split/split.component.html Prettier formatting adjustment in ngTemplateOutlet context object (trailing comma).
package.json Updates Prettier version and adds a prettier --write . script.
package-lock.json Locks Prettier to 3.8.1 with updated resolved/integrity metadata.
CONTRIBUTING.md Removes an extraneous blank line/whitespace in the guidelines list.
.github/workflows/license.yml Normalizes YAML indentation and quoting; removes trailing whitespace.
.github/workflows/dependency-review.yml No functional change; formatting/whitespace normalization.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Harpush
Copy link
Copy Markdown
Collaborator Author

Harpush commented Apr 3, 2026

I'm ok with this PR, but please update the description a bit, so we can address it properly when merging.

I am not sure what to add... It was only prettier version update and run it on all files

@SanderElias
Copy link
Copy Markdown
Contributor

@Harpush I just noticed that the type improvements also came from there. Surprising. But I'm fine with this.

@Harpush
Copy link
Copy Markdown
Collaborator Author

Harpush commented Apr 3, 2026

@SanderElias so do you want to merge or change semi to false? Or maybe more changes to prettier settings like print width back to 80?

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 this pull request may close these issues.

3 participants