Formats endpoint

— AP + DT + (FW)
This brings up the bigger question of how we manage features using flags and the support for turning those features off. How should we document these "features" and which flags are required? For example, today I was debugging why I couldn't create a new paper submission and lo and behold, it turned out that it was because I had event source ENV flag set to false. The submission succeeded but errored out on setting an event listener. :-/
 
As of the latest master, the downloads beyond just PDF and EPub become available as the supported iHat formats provide, which are generated at server boot. I can't find the business requirements to support that, however.

> On Dec 3, 2014, at 17:54, neo-tahi <notifications@github.com> wrote:
> 
> In config/initializers/ihat_supported_formats.rb:
> 
> > @@ -1,6 +1,7 @@
> >  Tahi::Application.config.ihat_supported_formats = 'null'
> >  module IhatSupportedFormats
> >    def self.call
> > +    # TODO use ENV.fetch; is there ever a time they wouldn't want to use iHat?
> The problem is that I'm pretty sure that things will break without it. Is this written down anywhere / are you sure about this? There are a lot of things that seem to be optional in the project but that cause breakage when they aren't there.
> 
> I'd rather have one big thing with services that are all required, than a crazy number of combinations of things that are all "optional", but break when removed.
> 
> \
> Reply to this email directly or view it on GitHub.
>