Jayson Vantuyl

@homeway FYI, I merged in a modified version your feature. It will come out in the next release. Basically, using a file named something like `name.py`: ``` title Some File...

@smwht When the next release comes out, `title ` boop should work.

I agree. It's likely to be more performant, too (if only slightly). That said, I think this wouldn't be backwards-incompatible. Anyone that previously detects a missing aggregate correctly will have...

I understand it to mean: "Asking for an aggregate with an ID that doesn't correspond to any known aggregate." The intuition here is that returning effectively an empty struct makes...

@fahchen For what it's worth, this is why I tend to have my enums default to an `UNKNOWN` value. It helps distinguish the zero value from a fresh but initialized...

@yordis Maybe I'm just misunderstanding the use-case. How exactly is the `aggregate_state/3` meant to be used?

> @jvantuyl I agree with you that we can have an unknown status as the initial flag. However, if we could identify the initial state, even without altering any bytes...

This isn't really necessary. If someone wants the `:aggregate_state` along with other information, they can ask for an `:execution_result` and pull it out of there.

Oh, I see. I was thinking you meant "after dispatch" semantically. Not the `after_dispatch` phase of the middleware. Nevermind, I see what you're getting at now.

## TL;DR How about this shell script? Put it in the PATH as `protoc-gen-elixir` and make sure you run `protoc` from within your project. ```sh #!/bin/sh -e ( mix deps.compile...