Prettier is an opinionated code formatter
Runs prettier as an eslint rule
Utilities to help expose prettier output in linting tools
Turns off all rules that are unnecessary or might conflict with Prettier.
Svelte plugin for prettier
Runs prettier as an stylelint rule
Integrate Prettier into Volar
A Prettier plugin for sorting Tailwind CSS classes.
Format code using Prettier
prettier plugin for XML
Synchronous version of Prettier
Prettier Oxc plugin.
Prettier Java Plugin
eslint-config-prettier for create-vue
Formats your JavaScript using prettier followed by eslint --fix
WordPress Prettier shared configuration.
A Prettier Plugin for formatting Astro files
Prettier package.json plugin to make the order of properties nice.
Make prettier organize your imports using the TypeScript language service API.
Prettier PHP Plugin
CLI for prettier-eslint
Do you wanna use tslint and prettier without conflicts? tslint-config-prettier disables all conflicting rules that may cause such problems. Prettier takes care of formatting and tslint the rest.
Salesforce Apex plugin for Prettier
Concurrent prettier runner
Opinionated code formatter - `cargo fmt` alternative (Community) (WIP)
Format //! and /// comments with prettier
A blazingly fast and safe, zero-allocation, `no_std`-compatible byte formatter.
A Rust tool to list directories and files in a tree-like structure with customizable display options.
🌈 Prettier-printed debug strings 🌈
CLI pipe uber/zap golang logs (JSON) to pretty terminal colors
Blazing fast Git hooks manager written in Rust. Drop-in replacement for Husky with 27x faster startup.
MoosicBox clippier package
Format, and lint, markdown code snippets using your favorite tools
A minimal `syn` syntax tree pretty-printer
External-formatter dispatch for hjkl: rustfmt, prettier, gofmt, ruff, stylua, shfmt, taplo and more
An Salesforce Apex lang formatter
prettier plugin for the Ruby programming language
A drop-in replacement for the prettyprint gem with more functionality.
Pronto runner for checking if the given files are formatted using Prettier
Turns off all rules that are unnecessary or might conflict with prettier plugin ruby.
Jekyll (Ruby static website generator) plugin that runs prettier on generated outputs.
The rails-routes-prettier gem makes it easy to view the routes in your Rails application. It converts the routes into a clear and readable format, making it simple to understand the structure of your application's routing. Whether you're a beginner or an experienced Rails developer, this gem is a valuable tool for navigating and understanding the routes in your application
A simpler, prettier Doxygen replacement.
Prettier element traversal with Nokogiri
Enables you to make good looking terminal programs with colors and text formatting.
Tools for building nice looking CLI applications
Prettier element traversal with Nokogiri
# Addy Allows pretty summations. Instead of writing: (1..5).inject(0) do |memo, num| memo + (num**num) end You write: sum(1..5) do |num| num**num end Personally, I would rather write the latter. ## Usage Install the gem: gem install addy Then use it! require 'addy' class MyClass #include it in a class or in Object to get it everywhere include Addy def my_awesome_adder(range) sum(range) end end When you include addy on a class that implements inject, you don't even need to pass a value to it. Instead it calls sum on your class. require 'addy' class MyClass < Range include Addy def my_awesome_adder sum end end ### Calling It You can call either sum or summation. They're aliases for the same thing. Note: The following assumes Addy is included into Range. When you pass a block to sum it will execute the block on the current number before adding it to the sum. sum(1..5) {|num| num + 1} #=> 20 (1..5).sum {|num| num + 1} #=> 20 You don't have to pass a block though! #this sum(1..5) #=> 15 #and (1..5).sum #=> 15 #are equivalent to sum(1..5) {|num| num} #=> 15 #and (1..5).sum {|num| num} #=> 15 ### Input Ranges and numeric arrays both work well. sum(1..5) #=> 15 sum([1,2,3,4,5]) #=> 15 ## Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. ## Copyright Copyright (c) 2010 Allen Madsen. See LICENSE for details. PS: Isn't it ridiculous how much documentation I wrote for one function?
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.