clojure-style-guide
ESLint
Our great sponsors
clojure-style-guide | ESLint | |
---|---|---|
15 | 379 | |
3,974 | 24,231 | |
- | 1.0% | |
2.9 | 9.7 | |
about 2 months ago | 6 days ago | |
JavaScript | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
clojure-style-guide
-
XML is better than YAML
Fixed link to that style guide entry: https://guide.clojure.style/#opt-commas-in-map-literals
Per that style guide, the above map would be formatted like this (on HN, just indent by two spaces):
{:a 1
-
How to be more idiomatic?
As for the broader question of Clojure style, there are style guides like https://github.com/bbatsov/clojure-style-guide and tools like clj-kondo to help learn and reinforce important practices.
-
What makes Clojure better than X for you?
Basically, you learn the expected places to put whitespace, make sure to edit your code accordingly and all of the parens will be automatically closed and adjusted. Using parinfer—which you can also combine with the more traditional paredit—makes writing Clojure code a lot like writing Python.
-
Poignant perspective I found about Clojure's community in r/ExperiencedDevs
Also, there are guidelines, the styleguide, clj-kondo, kibit etc. And if you don't review your interns/juniors code to teach them good practices - you're doing it wrong (well, this one is true for any practical PL out there).
-
How to learn Clojure idioms?
Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.
-
4-space indents?
It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-guide
-
Clojure Coding Guide
The same could be said about the "Clojure Style Guide" from the Cider guy. As a matter of fact, there was an issue about it that was quickly declined https://github.com/bbatsov/clojure-style-guide/issues/232
-
Wrote one of my first clojure programs (tic-tac-toe). Any constructive criticism would be greatly appreciated.
Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw
- Want to get into closure, but struck at practice
- [clojure-noob][code-review]I've written my first piece of code in clojure, can you guys review it ?
ESLint
-
To Review or Not to Review: The Debate on Mandatory Code Reviews
Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.
-
Biome.js : Prettier+ESLint killer ?
If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.
-
Most basic code formatting
eslint is used to avoid code errors
-
How to use Lefthooks in your node project?
No lint errors: The committed code does not contain any lint errors (eslint).
-
Git Project Configuration With Husky and ESLint
Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.
-
What is an Abstract Syntax Tree in Programming?
GitHub | Website
-
Shared Tailwind Setup For Micro Frontend Application with Nx Workspace
ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript.
-
6 Tools To Help Keep Your Dependencies And Code More Secure
ESLint
-
Six Factors That Raise The Risk Of Bugs In A Codebase
1. Lack of Static Code Analysis Static code analysis tools like TypeScript and ESLint play a crucial role in identifying and preventing bugs. TypeScript provides static typing, enhancing the robustness of the code. ESLint detects issues and enforces coding standards. The absence of these tools can significantly elevate the likelihood of bugs due to the lack of early detection and guidance provided during development.
-
Linting
The industry standard for JavaScript is ESLint. VS Code has an ESLint extension. Here is a guide.
What are some alternatives?
prettier - Prettier is an opinionated code formatter.
XO - ❤️ JavaScript/TypeScript linter (ESLint wrapper) with great defaults
Crafting Interpreters - Repository for the book "Crafting Interpreters"
Standard - 🌟 JavaScript Style Guide, with linter & automatic code fixer
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
30-days-of-elixir - A walk through the Elixir language in 30 exercises.
JSHint - JSHint is a tool that helps to detect errors and potential problems in your JavaScript code
Kalman-and-Bayesian-Filters-in-Python - Kalman Filter book using Jupyter Notebook. Focuses on building intuition and experience, not formal proofs. Includes Kalman filters,extended Kalman filters, unscented Kalman filters, particle filters, and more. All exercises include solutions.
JSLint - JSLint, The JavaScript Code Quality and Coverage Tool
papers-we-love - Papers from the computer science community to read and discuss.
Babel (Formerly 6to5) - 🐠 Babel is a compiler for writing next generation JavaScript.