Feature add plugins

[sebkolind]

This will allow users to specify a list of plugins to add before running prettier on their files. I have used this on Volcano more specifically here

Closes #22

[sebkolind]

I do realize that this is a very simple and somewhat naive way of doing this, since you could potentially install anything you want. So a check on the packages with regex, checking a pattern like @prettier/x-y-z might be a good idea.

Update

I added a check of the plugins' names with regex.

[creyD]

Looks extremely good! Thanks so much for your contribution! I will test this myself and then merge it.

[sebkolind]

@creyD Thank you! And you are welcome.

Out of curiosity - how do you test Actions locally? I've been having a workflow where I make a change, push to a branch, release a new version, and then test it in a separate project. This is extremely cumbersome😂 I can only imagine there is a better way of doing this?

[creyD]

I am not an expert at this, but here is my process: I test the commands locally (without the yml parameters ...) and then I create a test GitHub repo where I write uses: creyD/prettier_action@dev in the config. This does at least avoids the release cycle.

[creyD]

Your new release I tested in this: https://github.com/creyD/prettier_test , will delete this later.

[sebkolind]

Ahh I see. I was looking for a way of doing something like: uses: ../action/on/machine and use the action from a local directory or something like this. But I don't think that is possible, unfortunately.

Well, anyways, thanks!