gory 0.1.7

Add a little color to the task
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104

# gory
[![license-badge](https://img.shields.io/crates/l/fungus.svg)](https://opensource.org/licenses/MIT)
[![build](https://github.com/phR0ze/gory/workflows/build/badge.svg?branch=main)](https://github.com/phR0ze/gory/actions)
[![codecov](https://codecov.io/gh/phR0ze/gory/branch/main/graph/badge.svg?token=3KnXWj0qTw)](https://codecov.io/gh/phR0ze/gory)
[![crates.io](https://img.shields.io/crates/v/gory.svg)](https://crates.io/crates/gory)
[![rust-version](https://img.shields.io/badge/rust-latest%20stable-blue.svg)](https://github.com/rust-lang/rust/releases)

Super simple with minimal dependencies; `gory` is intended to just add a little color to your task

**Example:**  
![Display colors](docs/images/colors.png)

### Quick links
* [Usage](#usage)
  * [Get String](#get-string)
  * [Control use](#control-use)
* [Contribute](#contribute)
  * [Git-Hook](#git-hook)
* [License](#license)
  * [Contribution](#contribution)
* [Backlog](#backlog)

## Usage <a name="usage"/></a>
1. Import `gory` into your project via `Cargo.toml`
   ```toml
   [dependencies]
   gory = "0.1"
   ```
2. Use all of `gory` as its simple and tiny
   ```rust
   use gory::*;
   ```
3. Call functions off the default `Colorable` types `String` and `&'static str`
   ```rust
   use gory::*;
   
   fn main() {
       print!("{}  ", format!("\\e[1;{}m", Color::Red).red());
       print!("{}  ", "red".red());
       println!();
   }
   ```

### Get String <a name="get-string"/></a>
To get the wrapped `String` out of a `ColorString` just dereference it.

```rust
use gory::*;

fn main() {
  let cstr = String::from("foo").red();
  assert!(String::from("foo"), *cstr);
}
```

### Control use <a name="control-use"/></a>
Color output can be enabled or disabled using the `TERM_COLOR` varible.

`gory` will automatically detect whether a terminal is attached and if so and `TERM_COLOR` is truthy
or not set it will automatically use color when specified to do so in the code. If `TERM_COLOR` is
set to something falsy color will not be emitted despited an attached tty or use of color functions
in the code.

Additionally however for testing or for other reasons it may be nice to force color to be enabled or
disabled regardless of the presence of a tty or the the env var. This can be done at runtime by
invoking the function `Color::force(val: Option<bool>)` and giving it `true` to force on and `false`
to force off and `None` to return to automatic control.

```rust
use gory::*;

fn main() {
  Color::force(Some(true));
  Color::force(Some(false));
  Color::force(None);
}
```

## Contribute <a name="Contribute"/></a>
Pull requests are always welcome. However understand that they will be evaluated purely on whether
or not the change fits with my goals/ideals for the project.

### Git-Hook <a name="git-hook"/></a>
Enable the git hooks to have automatic version increments
```bash
cd ~/Projects/gory
git config core.hooksPath .githooks
```

## License <a name="license"/></a>
This project is licensed under either of:
 * MIT license [LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT
 * Apache License, Version 2.0 [LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0

### Contribution <a name="contribution"/></a>
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in
this project by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without
any additional terms or conditions.

---

## Backlog <a name="backlog"/></a>
* Support more pre-defined colors like `orange`?
* Support styles like `underline`?