Open Source Elixir Code Formatters

Livebook is a web application for writing interactive and collaborative code notebooks. Write notebooks in Livebook then securely deploy and share them with your team and company with Livebook Hub/Enterprise. Code notebooks with Markdown support and Code cells where Elixir code is evaluated on demand. Rich code editor through Monaco: with support for autocompletion, inline documentation, code formatting, etc. Interactive results via Kino: display Vega-Lite charts, tables, maps, and more. Automation: use Smart cells to perform high-level tasks and write notebooks faster than ever. Query databases, plot charts, build maps, and more directly from Livebook's UI. Reproducible: Livebook ensures your code runs in a predictable order, all the way down to package management. It also tracks your notebook state, annotating which parts are stale. Collaboration: multiple users can work on the same notebook at once, no additional setup is required.

This is community style guide for the Elixir programming language. Please feel free to make pull requests and suggestions, and be a part of Elixir's vibrant community. If you're looking for other projects to contribute to please see the Hex package manager site. Elixir v1.6 introduced a Code Formatter and Mix format task. The formatter should be preferred for all new projects and source code. The rules in this section are applied automatically by the code formatter, but are provided here as examples of the preferred style. Use Unix-style line endings (*BSD/Solaris/Linux/OSX users are covered by default, Windows users have to be extra careful). Use spaces around operators, after commas, colons and semicolons. Do not put spaces around matched pairs like brackets, parentheses, etc. Whitespace might be (mostly) irrelevant to the Elixir runtime, but its proper use is the key to writing easily readable code.