Shaun Smith

I agree with the goal of extracting all language specific logic from the CLI and relying on the generation of an appropriate Dockerfile. See #369 for comments on `init`. +1...

I got the latest CLI build with the new `init --init-image` support and was disappointed that the output didn't include a Dockerfile. 😞 @mjg123 I'm +1 for your original proposal...

Agreed. This is a missing feature. And `fn push` should probably also support `--all`.

The error is pretty clear that an attempt to convert null to an an object failed. Null input should result in a null object passed to the function handler. `...

@rikgibson can you take a look at this? I'd rather we fixed this bug than have to add warning text to the Java tutorial (https://github.com/fnproject/tutorials/pull/149).

Two issues @owencliffe. The native images don't pass on the build script args to the docker build command so passing "--squash" won't have any effect. The build-native script expects the...

I'm on the side of brevity when possible. David's point that we provide both verbose and abbreviated keywords in the CLI is well taken so why not also support aliases...

In terms of "niche" we've discussed migrating entirely to init images and making `fn init --runtime ` syntactic sugar for invoking a specific image. I actually think this feature is...

Right now an init-image only takes one input, function name, but it could take more like final image name. But since all we're doing is generating boilerplate we'd have to...

When running locally, `curl http://localhost:8080/invoke/` will let you invoke any function if you know its id. The root URL may vary by application so if you know the id of...