feat: add template options

[janbiasi]

Take a look at #12 for all details

CLI

• adding optional --css-template flag
• adding optional --html-template flag
• adding optional --sass-template flag
• adding optional --scss-template flag

Module

• adding an optional template object where you can define template paths for custom CSS, HTML, SASS and SCSS templates
• adding tests for the SASS and SCSS generators
• resolve templates from process.cwd() per default if the path is not absolute

SASS & SCSS templates

By default it will generate a variable for the font name ($<name>-font) as well as a map for the icons ($<name>-map) so the developers can pick their icon via map-get($example-map, 'my-icon')

[casaper]

oh, @janbiasi seems that we both did the same thing. Probably different, but however... 😉

see #18

Samesame but different. E.g. you added sass indented, I only did scss.
On the other hand I did allot of other stuff...

However. Looks good, at first glance.

[tancredi]

Hi @janbiasi - thank you so much for the PR! It looks really good, though there are just a few things I'd like to change, one you may not like, so here it is:

While adding option maps for different asset types (pathOptions and formatOptions) I made a conscious choice not to make them available to the client, for the simple reason that I'd like to expand asset types quite a bit (defaults would probably remain just a few of the assets, but I'd like people to contribute more built-in templates etc etc.) and if we added that in it would just becomes a very fast increasing list (loads of options, loads to maintain)

I'd rather leave granular control to the config file, so you could specify options, custom paths and templates for each individual asset type only by defining it in JSON in the .fantasticonrc

How does that sound, reasonable?

[tancredi]

This makes tests and mocks fallback to default TS config, which generates warnings and is quite unpredictable - would rather add this change it test files had their own configuration.

[janbiasi]

I agree, it would make sense to have a tsconfig.test.json for the test files; I've excluded the mocks and tests because they were also compiled and were included in the compiled output which isn't very great imo 😅

[tancredi]

For the time being I merged with a couple of changes (no cli options), so you can start using it but only with the config / API - but I'd like to keep the conversation open, it was more to get this out soon as it's very good stuff and other PRs depend on it :)

Available in version 1.0.14

[janbiasi]

Thanks a lot for the positive feedback, really appreciate it :) And as you mentioned, I totally forgot about the CLI options 🤦 my fault, sorry! And in regards of the tsconfig; I'll reply above to your feedback :)

[saiballo]

We use icon-font-generator in same bash scripts with cpoint option called in line command. In fantasticon I would have preferred to access it via CLI and not in a config file...

by the way you are the main dev :-)