Add Dockerfile for testing.

[JayDoubleu]

No description provided.

[TylerLeonhardt]

Can you add a comment maybe at the top, that tells how to use this Dockerfile especially mentioning the:

runuser -l nvim -c 'nvim test.ps1'

[TylerLeonhardt]

Perhaps we should change this to pwsh since... It's a PowerShell container 😁

[JayDoubleu]

How does it look now ?
Amended with both suggestions.

[corbob]

🤔 I wonder if we should add a comment to the file for those that are new to docker to explain how to build the image and run it. (AKA: I don't know docker, so I had to go find where it was referenced in the initial issue to see how to build a docker file.)

[JayDoubleu]

I was thinking the same thing actually. I was about to add building instructions for Windows/Linux and Mac into the README.md itself of that directory. I think it would be best if guys would specify where should this actually reside. Currently its in tests/Docker which technically could have a really nice README inside instead of using comments inside Dockerfile. I guess the wiki pages is always a good option. There is even a nice way to alias docker images like shown here:
https://github.com/alexjc/neural-enhance#2-installation--setup

alias enhance='function ne() { docker run --rm -v "$(pwd)/`dirname ${@:$#}`":/ne/input -it alexjc/neural-enhance ${@:1:$#-1} "input/`basename ${@:$#}`"; }; ne'

[TylerLeonhardt]

I like the idea of adding a small section to the README. That tells you how to run the Dockerfile. Just simply:

• Build
• Run
• and then the runuser -l nvim -c 'nvim test.ps1' commands

And instead, if we can move the Dockerfile to a tools folder, I think that makes a bit more sense IMO. We’ll put tests under tests…….. eventually

[corbob]

🤔 Is there any particular reason for us to have a nvim and a vim user? Would it not make more sense to just have a single user that has both configs?

[JayDoubleu]

The only reason why there is both users inside is to provide full isolation of user profiles for testing. Aka nothing from nvim can affect vim testing and vice versa. Might not be exactly necessary tbh. I just find this logical decoupling useful for example if I would accidentally point my nvim config at .vim/plugged rather than other location etc.

[corbob]

With the addition of snippets in #55 we might want to consider adding coc-snippets to the CocInstall lines... Perhaps including coc-json (recommended by coc.nvim for editing CocConfig.

[TylerLeonhardt]

#55 is in now, @JayDoubleu if you don't mind updating this PR with the 2 additional packages

[JayDoubleu]

Sure thing. Will update soon with new folder structure etc.

[TylerLeonhardt]

LGTM! Awesome work @JayDoubleu

[corbob]

There was discussion of adding the steps to run the docker to the ReadMe. Do we want to do that in this change, or do we want to do it in a separate change?

[corbob]

Because we have a vim and nvim user, could we store the plugins in the same spot for both users, and then instead of duplicating this code, we could write it to a common file and copy that file to the proper spot for each user?

[TylerLeonhardt]

Not sure if the extensions (and coc) expect certain things to be in certain places... But this would bring the package down. Let's defer this for now.

[TylerLeonhardt]

@corbob a separate PR is probably fine for that