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

(Feature request) Add eslint #2324

Closed
1 task done
Myzel394 opened this issue Nov 10, 2021 · 6 comments
Closed
1 task done

(Feature request) Add eslint #2324

Myzel394 opened this issue Nov 10, 2021 · 6 comments

Comments

@Myzel394
Copy link
Contributor

Preflight Checklist

  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe feature

A linter helps us having consistent code design

Additional Information

No response

@Myzel394
Copy link
Contributor Author

@zadam what do you think?

@zadam
Copy link
Owner

zadam commented Nov 24, 2021

I'm fine with it as an advisory tool, but not as a pre commit hook, auto formatter etc.

Also of course depends on the rule set.

@Myzel394
Copy link
Contributor Author

I'm fine with it as an advisory tool, but not as a pre commit hook, auto formatter etc.

Why not? I think that would help us having a consistent codebase. For example: Double quotes or single quotes? Currently we use both kind of, which is a bit messy. With an auto formatter, we'd have it consistent.

@zadam
Copy link
Owner

zadam commented Nov 26, 2021

It's a bikeshedding most of the time. "consistency" is in itself very vague goal without a clear practical benefit.

@Myzel394
Copy link
Contributor Author

It's a bikeshedding most of the time

I agree with small projects, but for such a large app like Trilium Notes, I think it would be very beneficial.

"consistency" is in itself very vague goal without a clear practical benefit.

The benefit is that we will need less cognitive power to read the code because everything is formatted in a way we understand. This way, we can focus on the actual implementations and their problems, instead of trying to understand the code before we can actually implement it.

@meichthys
Copy link
Collaborator

Trilium has entered maintenance mode. Future enhancements will be addressed in TrilumNext: TriliumNext#138

@meichthys meichthys closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants