Fix base permissionConfig to match Pro and ePA variants (by removing it)

[nico-famedly]

Pull Request Details

Provide details about your pull request and what it adds, fixes, or changes.

In #259 domainExceptions was renamed to serverExceptions, but only in 2 of the 3 schemas. To avoid confusion update the third schema to match the others by removing it. It isn't referenced by any active specifications anymore.

Breaking Changes

Describe what features are broken by this pull request and why, if any.

<Content>

Issues Fixed

Enter the issue numbers resolved by this pull request below, if any.

<Content>

Other Relevant Information

Provide any other important details below.

This is potentially a breaking change? I don't know why there are 3 schemas and there might be an additional process to follow here, but I think the linked PR should help with that?

[Johennes]

The situation is slightly confusing. The permissionConfig.json was not changed because it was used in gemProdT_TI-M_Client_ePA_PTV_1.0.0-0_V1.0.0 (via TI-M Basis 1.0.0). This release has since been discontinued, however. So I think we can just remove this file entirely on develop.

[nico-famedly]

I can do that. It is just confusing since TI-M Basis also references invite permissions and now there would be no schema for that. But it doesn't really matter to me either way :)

[jason-famedly]

Is this file important in this context?
https://github.com/gematik/api-ti-messenger/blob/main/src/schema/examples/permissionConfig.domain-exception.json

[Johennes]

I can do that. It is just confusing since TI-M Basis also references invite permissions and now there would be no schema for that.

Yes, like I said, it's very confusing. 🙈

The specs themselves don't give versions for the documents they reference. So TI-M Basis 1.0.0 references permissionConfig.json from "https://github.com/gematik/api-ti-messenger". The version is only specified in the "Produkttypsteckbrief" that uses specs to define a concrete product type.

The only "Produkttypsteckbrief" that uses TI-M Basis 1.0.0 is gemProdT_TI-M_Client_ePA_PTV_1.0.0-0_V1.0.0 and this links to permissionConfig.json at 9b9f21b.

So it is possible to get to the old permissionConfig.json from there. It's not great but I think this is better than keeping the file around on develop / main indefinitely.

[Johennes]

Is this file important in this context? https://github.com/gematik/api-ti-messenger/blob/main/src/schema/examples/permissionConfig.domain-exception.json

Err, yes I guess we can kill the examples, too, then. Good call.

We're also about to kill develop entirely with #313. So the base branch of this PR would need to change. @nico-famedly if this is getting too tedious, feel free to abandon it and I can just nuke the files myself on main after the merge.

[nico-famedly]

Well, it is not getting to tedious, but it will probably be easier for you to change directly than me trying to catch up. So I will just close it and you fix it directly? :)

[Johennes]

Ok, yeah let me just handle it directly. I'll keep the PR open until then as a reminder. Thanks for surfacing the issue in any case! 🙏