amitaibu

Happy to see another great release!

I tried to keep the code simple, so yeah - it was on the expense of making it more "right".

In this case I wouldn't call the command send the mail unless status was explicitly Accepted or Rejected.

But as notes above, the important part is that the compiler doesn't let me forget about all the possible cases (e.g. `Queue` in this example).

I can relate! :)

@turnipla Indeed, the Elasticsearch is completely a typical request - response kind. However, the point in the post was showing how we could make sure the search is in full sync with static site - even if we for example rolled-back deploys. That is, even if we rollback to a revision with less content than what we have in the "default" index, search will not show it to us.

@arkadiyt Thanks - I see your point. However, I believe you can also think about it as a service - similar to how Disqus can be added to your static site. That is, the site is static, but the results for the search are handled with a service. In this case the "service" - Elasticsearch - is tightly coupled to your static site's revision.