## ascii-art-fs
### Objectives
You must follow the same [instructions ](https://public.01-edu.org/subjects/ascii-art/ ) as in the first subject but the second argument must be the name of the template.
This project will help you learn about :
- The Go file system(**fs**) API.
- Ways to receive data.
- Ways to output data.
- Manipulation of strings.
- Manipulation of structures.
### 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 should present a **test file** .
- You can see all about the **banners** [here ](https://github.com/01-edu/public/tree/master/subjects/ascii-art ).
### Allowed packages
- Only the [standard go ](https://golang.org/pkg/ ) packages are allowed
### Usage
```console
$ go run . "hello" standard
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.
4 years ago
_ _ _
| | | | | |
| |__ ___ | | | | ___
| _ \ / _ \ | | | | / _ \
| | | | | __ / | | | | | (_) |
|_| |_| \___| |_| |_| \___/
$ go run . "Hello There!" shadow
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.
4 years ago
_| _| _ | _| _ |_|_|_|_| _| _ |
_| _| _ |_| _| _ | _|_ | _| _ |_|_| _|_ | _| _ |_| _|_ | _|
_|_|_|_| _|_ |_|_| _| _ | _| _ | _| _ | _| _ |_|_|_| _|_ | _|_ |_|_| _|
_| _| _ | _| _ | _| _ | _| _ | _| _ | _| _ |
_| _| _ |_|_| _| _ | _|_ | _| _ | _| _ |_|_| _| _ |_|_| _|
$ go run . "Hello There!" thinkertoy
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.
4 years ago
o o o o o-O-o o
| | | | | | o
O--O o-o | | o-o | O--o o-o o-o o-o |
| | |-' | | | | | | | |-' | |-' o
o o o-o o o o-o o o o o-o o o-o
O
$
```
