FHIR Chat · do we need to restrict allowedBundleTypes · hapi

Stream: hapi

Topic: do we need to restrict allowedBundleTypes


view this post on Zulip Patrick Werner (Sep 12 2019 at 15:36):

I'm currently creating a PR for the jpaserver-starter to allow to specify the allowedBundleTypes for persistence in the property file. Now i am wondering why there is a restriction in hapi for that in the first place? Wouldn't it be easier to allow all BundlTypes (all but NULL)?

view this post on Zulip Patrick Werner (Sep 12 2019 at 15:38):

use-cases are IG related, e.g. uploading an Example Transaction Bundle. I think @Sean McIlvenna needs this functionality for trifolia as well. Otherwise you can't build IGs with Bundle examples. @James Agnew

view this post on Zulip James Agnew (Sep 12 2019 at 15:51):

FWIW: I added that restriction initially because I was sick of people
complaining that HAPI didn't support transactions properly when in fact
they were incorrectly POSTing their transaction bundles to /Bundle.. This
is a very common mistake it seems.

view this post on Zulip Patrick Werner (Sep 12 2019 at 16:43):

ah! ok thats a valid usecase. I'll push a PR for jpa-starter later today then. So everyone who needs the functionality can use it, but the default stays the same. Saving you from too much support buzz.

view this post on Zulip Patrick Werner (Sep 12 2019 at 18:13):

https://github.com/hapifhir/hapi-fhir-jpaserver-starter/pull/51

view this post on Zulip Patrick Werner (Sep 12 2019 at 18:13):

also added google codestyle (in .idea) as there was no codestyle present

view this post on Zulip Patrick Werner (Sep 12 2019 at 18:15):

@Sean McIlvenna propably relevant for trifolia on fhir IG editing


Last updated: Apr 12 2022 at 19:14 UTC