Implement issue template

[StefanVDWeide]

Hi!

I've been looking for a good ingredient parsing library for a while and found that a lot of them either aren't maintained anymore or have features fragmented over different forks with no intention to merge back. This project has good potential to become the standard ingredient parsing library!

Now, if this library gets more populair it would be a good idea to have an issue template so that everything is nice and clean.

Details on how to implement this can be found here:

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Let me know what you think!

[jakeboone02]

Thanks for your interest in the library! With a grand total of 30 downloads on npm in the last 7 days, 8 stars on GitHub, and #5 being the very first issue raised after its initial release more than two years ago...I'm not really sure that I would benefit a great deal from an issue template.

I do appreciate your enthusiasm, though! I'm quite proud of this library and its companion packages numeric-quantity and format-quantity, even considering their low engagement numbers.

[jakeboone02]

FYI: v0.6.0

[dRoskar]

Hello to both.
I've also taken interest in this library. The reason I am reaching out here is because of the change you mentioned in this thread. Adding "small", "medium" and "large" to the units list breaks this library for me. When the ingredients list says "2 large eggs" the unit of measure should be null, in my opinion. I don't quite understand how adjectives became units of measure.
But in case this is needed for some use case that I'm not aware of, at least it would be great to give users the option to exclude certain units of measure from the list, just like we can add them.
Best regards

[jakeboone02]

@dRoskar That's a good point about adjectives not being units of measure. I think it works in this case because it can imply a particular amount of something, not just a relative size. For example, chicken eggs have to be within very specific mass limits to be labeled as "small"/"medium"/"large"/etc.

But I also think an "escape hatch" would be a nice feature. Maybe an array of strings to ignore when looking for units? Something like this:

parseIngredient('2 large eggs', { ignoreUOM: [ 'small', 'medium', 'large' ] })

What do you think?

[dRoskar]

I think that would work perfectly 👍

[jakeboone02]

See #17