Plugins & Contributions in Web Frontend Technology Stack

To reach the expected modularity, React components are assembled in a plugin/contribution pattern:

each module describes (in a manifest):

the extension points he contributes to (MainMenu, other components extension points,...)
the extension points to which other modules can contribute.

Overly simplified Examples:

Stating that the backend provides a dynamic REST API (see Online Backend Target Technology Stack for more details), with CRUD on the following model:

Here are some example of the contribution mechanism:

Claim list, with insuree information

Claim searcher, filtering on insuree data

... which can be summarised by the following diagram:

Comments

Patrick Delcroix

Jun 4, 2020

@Xavier Gillmann (Unlicensed)

For the formal sector, I will need contribution on children item which are not created yet, the trick is that contribution will depend on one of the variable of the parent.

To illustrate my issue I will take the claim example:

Saying that you want to have the price of an item from the health facility price list (claim → hf → Service Price List)

How could you call the contribution for that price when the neither the claim nor the claimService are created in the database ?

Thanks in advance