Skip to content

[Housekeeping] Replace prettier with stylistic, improve types, and add no-undef rule#1975

Merged
CarlosFdez merged 1 commit into
mainfrom
stylistic
Jun 5, 2026
Merged

[Housekeeping] Replace prettier with stylistic, improve types, and add no-undef rule#1975
CarlosFdez merged 1 commit into
mainfrom
stylistic

Conversation

@CarlosFdez
Copy link
Copy Markdown
Contributor

@CarlosFdez CarlosFdez commented Jun 5, 2026

Most changes are indentation based, since stylistic has different preferences. The main benefit is that now if you set up the symlinks so that foundry is linked up right, the types should more or less function and undeclared stuff should warn immediately.

No unused vars has a lot of violations so I didn't turn it on yet.

Other changes are:

  • Removed some unused code that had a lot of errors in it
  • Removed a function that was overwritten later in the fire
  • Replaced reject() for return on the party

@CarlosFdez CarlosFdez changed the title Replace prettier with stylistic, improve types, and add no-undef rule [Housekeeping] Replace prettier with stylistic, improve types, and add no-undef rule Jun 5, 2026
@WBHarry
Copy link
Copy Markdown
Contributor

WBHarry commented Jun 5, 2026

Hm..yah, I tested the current branch, setting up the symlink and all.

The autocompletion of CONFIG is definately there which is great.
I think you prolly forgot to push up a package change from eslint/prettier to stylistic tho. I don't see any reference of it in package.json, and I'm definately getting that console junk and stuff.

npm run lint gives 1250 errors and a tun of garbo blank space in the terminal 🙃

@CarlosFdez
Copy link
Copy Markdown
Contributor Author

Did you run npm ci? Interesting that you're getting garbo blank space without prettier though. Maybe the garbo blank space is by something else? It went away when I replaced prettier. Oh well, I prefer how stylistic handles nested ternaries better. The 2 space indentation was annoying.

Copy link
Copy Markdown
Contributor

@WBHarry WBHarry left a comment

Choose a reason for hiding this comment

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

Huh, well I'll be.
I was not aware of the difference between npm install and npm ci until I looked it up now. I ran install before - but clearly the reinstall was needed.

It works. And I generally like non-forced indentation, so it's all good with me 👍

@CarlosFdez
Copy link
Copy Markdown
Contributor Author

CarlosFdez commented Jun 5, 2026

Oh it still indents, but with a multiple of 4 instead of sometimes indenting by 2 because there's a ? in the expression.

I will get something in to make dev setup neater easier, but with this hopefully one type of error will cleanly not exist anymore, and now the jsdoc type stuff can actually work.

@CarlosFdez CarlosFdez merged commit a4428fd into main Jun 5, 2026
1 check passed
@CarlosFdez CarlosFdez deleted the stylistic branch June 5, 2026 19:53
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.

2 participants