chore: migrate eslint to flat config

[BBboy01]

use npx eslint --inspect-config browse all configured rules

ngx-quill/.eslintrc.json

Lines 3 to 5 in db73b0c

	"ignorePatterns": [
	"projects/**/*"
	],

previous ignore pattern ignored all ts files, eslint seems lint nothing

• remove unused plugins eslint-plugin-prefer-arrow and eslint-plugin-import
• replace @angular-eslint/* with angular-eslint
• '@typescript-eslint/no-explicit-any': 'off' as rule

[KillerCodeMonkey]

oh i never noticed, cause my code editor already is linting it on the fly

[BBboy01]

we dont need @eslint/js, it just provides languageOptions for js files, but we dont have a single js files and // @ts-check is much better

[BBboy01]

I noticed there is a .prettirerc file but no prettier as dependency, I'm not sure are you using prettier for code formatting

we can add prettier as lint rules too

[KillerCodeMonkey]

I noticed there is a .prettirerc file but no prettier as dependency, I'm not sure are you using prettier for code formatting

we can add prettier as lint rules too

i guess when using stylistic it is not a good thing to add prettier as well. they are more or less there for the same purpose.

[BBboy01]

i guess when using stylistic it is not a good thing to add prettier as well. they are more or less there for the same purpose.

Oh right, fair enough, leave it just as it is now

[KillerCodeMonkey]

can you check the ci and ping me, if you think the pr is ready?

PS: nice to see/have a real life example with angular + stylistic. In other projects i hate to touch those things...

[BBboy01]

@KillerCodeMonkey it's ok now, seems like my global npm proxy caused the error

[KillerCodeMonkey]

@BBboy01 thanks 👍

[BBboy01]

https://ngxtension.netlify.app/utilities/migrations/inject-migration/

if you like, we can easily use ngxtenstion provided script to migrate angular decorators to signals

[KillerCodeMonkey]

currently for inputs input signals are used. i am waiting til "model" signals are stable and replace some input with model signals.

for outputs some more refactorings need be done, cause we are adding and triggering some outputs only if there are observers. So i need to check, if we need this logic at all and if, how we can adapt it with signals.