[feature] Add support for line breaks

[MikeCrookes]

Would be great to be able to add line breaks into the fields as long descriptions can extend the output past normal screen width

[formatc1702]

This sounds reasonable. Which fields in particular are you thinking of?
Surely the notes fields... any other? I wouldn't want the code to become too cluttered with too many \n to <br> conversions all over the place.

[MikeCrookes]

I'm not that familiar with all the fields (and what they do) but looking at the data classes I think may be useful for;

• name
• category
• type
• subtype
• notes (as you suggested)

[formatc1702]

I have started some work in the feature/linebreaks branch.
Here's the YAML file I'm using to test.

I will add support for the following fields:

• type
• subtype
• notes

name is the unique designator for a component and should be short and sweet (e.g. X1), no need for line breaks.
cagegory is only used internally, currently to distinguish between connectors and ferrules, as well as between cables and wire bundles. Thus the user does not need to edit this field.

Coming up: Replace line breaks with spaces for BOM output

[formatc1702]

Closed by #64.