A separate endpoint, then? That would be cleaner.
On Thu, Feb 24, 2022 at 6:31 AM Nick Burch <[email protected]> wrote: > > On Tue, 22 Feb 2022, Tim Allison wrote: > > I guess the question is how far do we want to bake this in? I could see > > adding a field for the default extension in the > > CompositeDetector/DefaultDetector. This would then be triggered on > > embedded files, too. I can't imagine this would add much cost > > computationally(???), and it would just show up for free all over the > > place. > > Ah, I thought this would be something that required two API hits. Having > done your detection or parsing, you'd then query a mimetype related API to > get extra details on the type you were told your file was. > > You could also pre-check types you think you'd be interested in, or grab > all the details on all the types, if you so wanted > > Nick
