## ascii-art
### Objectives
Ascii-art consists on receiving a `string` as an argument and outputting the `string` in a graphic representation of ASCII.
- This project should handle numbers, letters, spaces, special characters and `\n` .
- Take a look at the ASCII manual.
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 present a **test file** .
- It will be given some [**banner** ](https://github.com/01-edu/public/blob/master/subjects/ascii-art ) files with a specific graphical template representation of ASCII. The files are formatted in a way that it is not necessary to change them.
### Banner Format
- Each character has an height of 8 lines.
- Characters are separated by a new line `\n` .
- Here is an example of ' ', '!' and '"'(one dot represents one space) :
```console
......
......
......
......
......
......
......
......
._..
|.|.
|.|.
|.|.
|_|.
(_).
....
....
._._..
(.|.).
.V.V..
......
......
......
......
......
etc
```
### Allowed packages
- Only the [standard go ](https://golang.org/pkg/ ) packages are allowed
### Usage
```console
$ go run . "hello"
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
_ _ _
| | | | | |
| |__ ___ | | | | ___
| _ \ / _ \ | | | | / _ \
| | | | | __ / | | | | | (_) |
|_| |_| \___| |_| |_| \___/
$ go run . "HeLlO"
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
_ _ _ _ ____
| | | | | | | | / __ \
| |__| | ___ | | | | | | | |
| __ | / _ \ | | | | | | | |
| | | | | __ / | |____ | | | |__| |
|_| |_| \___| |______| |_| \____/
$ go run . "Hello There"
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
_ _ _ _ _______ _
| | | | | | | | |__ __ | | |
| |__| | ___ | | | | ___ | | | |__ ___ _ __ ___
| __ | / _ \ | | | | / _ \ | | | _ \ / _ \ | '__| / _ \
| | | | | __ / | | | | | (_) | | | | | | | | __ / | | | __ /
|_| |_| \___| |_| |_| \___/ |_| |_| |_| \___| |_| \___|
$ go run . "1Hello 2There"
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
_ _ _ _ _______ _
_ | | | | | | | | ____ |__ __ | | |
/ | | |__| | ___ | | | | ___ |___ \ | | | |__ ___ _ __ ___
| | | __ | / _ \ | | | | / _ \ __ ) | | | | _ \ / _ \ | '__| / _ \
| | | | | | | __ / | | | | | (_) | / __ / | | | | | | | __ / | | | __ /
|_| |_| |_| \___| |_| |_| \___/ |_____| |_| |_| |_| \___| |_| \___|
$ go run . "{Hello There}"
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
__ _ _ _ _ _______ _ __
/ / | | | | | | | | |__ __ | | | \ \
| | | |__| | ___ | | | | ___ | | | |__ ___ _ __ ___ | |
/ / | __ | / _ \ | | | | / _ \ | | | _ \ / _ \ | '__| / _ \ \ \
\ \ | | | | | __ / | | | | | (_) | | | | | | | | __ / | | | __ / / /
| | |_| |_| \___| |_| |_| \___/ |_| |_| |_| \___| |_| \___| | |
\_\ /_/
$
```
