Gustavo Bicalho

I'd love to get a review from the people involved in https://github.com/microsoft/vscode-dev-containers/pull/685 @jneira @stuartpike @eitsupi

@eitsupi thanks for the feedback! Changes: * Shaved some dependencies that were indeed installed by common-debian, or that did not seem to be really necessary (I was able build some...

@stuartpike The existing devcontainer image does not work at all right now (it does not include a HLS binary to power the VSCode Haskell extension). That's why I think it...

Since this is the `vscode-dev-containers` repo, I think the priority should be to have a Dockerfile that enables Haskell development in VSCode out of the box. Because of the change...

> What type of development are you wanting to do with this? > > * building and packaging Haskell libraries and programs (cabal) > * build Haskell projects and manage...

Hi @bamurtaugh thanks for the info! Does this mean we cannot merge this PR, and we have to wait for the new template process?

Right. I will close this PR then. @bamurtaugh if I open a PR simply removing the existing container, would that be accepted? I think this would be better than the...

> But we'll also be discussing what to do with contributions in this repo that don't end up as part of the new repos, so perhaps we hold off until...

While we wait for a fix, here is a workaround (no sure if this is the best env var to check for, but it seems to work) ```elixir # Workaround...

Or we can just emit the relevant events on the present/push/pop/dismiss native methods instead of using the FragmentManager/UINavigationController events