## ascii-art-output
### Objectives
- You must follow the same [instructions ](https://public.01-edu.org/subjects/ascii-art/ ) as in the first subject **while** writing the result into a file.
- The file must be named by using the flag `--output=<fileName.txt>` , in which `--output` is the flag and `<fileName.txt>` is the file name.
This project will help you learn about :
- Client utilities.
- The Go file system(**fs**) API.
- Ways to receive data.
- Ways to output data.
- Manipulation of strings.
- Choices of outputs.
### Instructions
- Your project must be written in **Go** .
- The code must respect the [**good practices** ](https://public.01-edu.org/subjects/good-practices/ ).
- It is recommended that the code presents a **test file** .
### Allowed packages
- Only the [standard go ](https://golang.org/pkg/ ) packages are allowed
### Usage
```console
student@ubuntu:~/ascii-art$ go build
student@ubuntu:~/ascii-art$ ./ascii-art "hello" standard --output=banner.txt
student@ubuntu:~/ascii-art$ cat banner.txt
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
_ _ _
| | | | | |
| |__ ___ | | | | ___
| _ \ / _ \ | | | | / _ \
| | | | | __ / | | | | | (_) |
|_| |_| \___| |_| |_| \___/
student@ubuntu:~/ascii-art$ ./ascii-art "Hello There!" shadow --output=banner.txt
student@ubuntu:~/ascii-art$ cat banner.txt
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
_| _| _ | _| _ |_|_|_|_| _| _ |
_| _| _ |_| _| _ | _|_ | _| _ |_|_| _|_ | _| _ |_| _|_ | _|
_|_|_|_| _|_ |_|_| _| _ | _| _ | _| _ | _| _ |_|_|_| _|_ | _|_ |_|_| _|
_| _| _ | _| _ | _| _ | _| _ | _| _ | _| _ |
_| _| _ |_|_| _| _ | _|_ | _| _ | _| _ |_|_| _| _ |_|_| _|
student@ubuntu:~/ascii-art$
```