Download the PHP package schleuse/dindent without Composer
On this page you can find all versions of the php package schleuse/dindent. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download schleuse/dindent
More information about schleuse/dindent
Files in schleuse/dindent
Package dindent
Short Description Fork of gajus/dindent with various fixes from the community
License BSD-3-Clause
Homepage https://github.com/schleuse/dindent
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package dindent
Dindent
Dindent (aka., "HTML beautifier") will indent HTML for development and testing. Dedicated for those who suffer from reading a template engine produced markup.
Abuse Case
Dindent will not sanitize or otherwise manipulate your output beyond indentation.
If you are looking to remove malicious code or make sure that your document is standards compliant, consider the following alternatives:
If you need to indent your code in the development environment, beware that earlier mentioned libraries will attempt to fix your markup (that's their primary purpose; indentation is a by-product).
Regex
There is a good reason not to use regular expression to parse HTML. However, DOM parser will rebuild the whole HTML document. It will add missing tags, close open block tags, or remove anything that's not a valid HTML. This is what Tidy does, DOM, etc. This behavior is undesirable when debugging HTML output. Regex based parser will not rebuild the document. Dindent will only add indentation, without otherwise affecting the markup.
The above is also the reason why Chrome DevTools is not a direct replacement for Dindent.
Use
In the above example, [..] is a placeholder for:
Dindent will convert it to:
Options
Indenter constructor accepts the following options that control indentation:
| Name | Description |
|---|---|
indentation_character |
Character(s) used for indentation. Defaults to 4 whitespace characters. |
logging |
Keep Track of every transformation and verify. May be memory intensive. Defaults to false |
Set element type
HTML elements are either "inline" elements or "block-level" elements.
An inline element occupies only the space bounded by the tags that define the inline element. The following example demonstrates the inline element's influence:
A block-level element occupies the entire space of its parent element (container), thereby creating a "block." Browsers typically display the block-level element with a new line both before and after the element. The following example demonstrates the block-level element's influence:
Dindent identifies the following elements as "inline":
- b, big, i, small, tt
- abbr, acronym, cite, code, dfn, em, kbd, strong, samp, var
- a, bdo, br, img, span, sub, sup
This is a subset of the inline elements defined in the MDN.
All other elements are treated as block.
You can set element type to either block or inline using setElementType method:
CLI
Dindent can be used via the CLI script ./bin/dindent.php.
Known issues
- Does not treat comments nicely and IE conditional blocks.
Installation
The recommended way to use Dindent is through Composer.
All versions of dindent with dependencies
ext-mbstring Version *