Hello again Apollo!
I was working through these final lessons for federating the monolith and was dealing with some errors:
UNKNOWN: Field "Host.id" can only be defined once.
UNKNOWN: Field "Host.name" can only be defined once.
UNKNOWN: Field "Host.profilePicture" can only be defined once.
UNKNOWN: Field "Host.profileDescription" can only be defined once.
UNKNOWN: There can be only one type named "Host".
UNKNOWN: Field "Guest.id" can only be defined once.
UNKNOWN: Field "Guest.name" can only be defined once.
UNKNOWN: Field "Guest.profilePicture" can only be defined once.
UNKNOWN: There can be only one type named "Guest".
UNKNOWN: Field "Query.user" can only be defined once.
UNKNOWN: Field "Query.me" can only be defined once.
UNKNOWN: [monolith] Guest -> appears to be an entity but no @key directives are specified on the originating type.
UNKNOWN: [monolith] Host -> appears to be an entity but no @key directives are specified on the originating type.
and
error[E029]: Encountered 2 build errors while trying to build a supergraph.
Caused by:
Encountered 2 build errors while trying to build the supergraph.
UNKNOWN: Field "Query.user" can only be defined once.
UNKNOWN: Field "Query.me" can only be defined once.
After I back tracked through the lessons I figure out I missed a few key steps that were a bit “hidden” inside some collaspers.
It’s all good, as I was able to back track through my work, and it really shows the user how intricate this process is. One thing that could be useful is to have a lesson step, that would let the user do some final validation to review the subgraph-accounts
schema side by side with the monolith
schema to ensure they have made all the schema level changes to be able to run npm run compose
sucessfully.
Just a suggestion to consider.