Monorepo frontend backend contexts

[hinogi]

In a lot of cases you use same terms in frontend and backend but best practice seems to be to have a frontend context and a backend context.
What is the way to cross the gap between both?

[chrissimon-au]

If you are modelling the frontend and backend as separate contexts but want to share the terms, I think the simplest option would be to use the new import feature. In the frontend folder, import all the glossaries of backend contexts that share terminology with the front end. e.g.

/frontEnd
  /frontend.glossary.yml
  frontendcode.ts
/backend
  /contextA
    /contextA.glossary.yml
    /contextA.code.cs
  /contextA
    /contextB.glossary.yml
    /contextB.code.java

With frontend.glossary.yml containing:

imports:
  - "../backend/contextA/contextA.glossary.yml"
  - "../backend/contextB/contextB.glossary.yml"

In this way any term defined in either contextA or contextB would match in the frontend code - however, it would show the definition as belonging to either contextA or contextB (or both if they have the same terminology with different definitions).

This may not suit what you want, but since you say that the terms are the 'same', hopefully sharing the definitions is what you want?

If it isn't what you want, then perhaps that is a hint that while the words are the same, the definitions are subtly different, which means the frontend should have it's own glossary?

[hinogi]

Sharing the same Entity names in Frontend and backend makes sense to me especially when the graphql schema uses the same terms and the generated graphql operations also include those terms, like useSomeGraphQLOperationNameQuery or useSomeGraphQLOperationNameMutation

[chrissimon-au]

And can I check, do you have terms from multiple bounded contexts appearing in your frontend code?

[hinogi]

since import doesn't work I cannot try this.

[chrissimon-au]

Sorry, to clarify, I meant does your frontend source code contain terms where it would be helpful to have access to terminology definitions from multiple backend bounded contexts?

Apologies for the issues you're facing with import - I'm sure it won't be too much longer to get them resolved for you!

[hinogi]

Sure, frontend and backend share the graphql schema so they also share the terms