After going back and forward though the module exercises trying to figure out what’s not working, it looks like there’s a few issues?
First issue is that in 4.16 Exercise 6, step 7 it says:
Hint: note that it’s using the ContentDocument interface. You might need to adjust it as well or create a new interface for the FAQContent document fields in the “brx.d.ts” file
In the explanation video (4.17 Exercise 6) doesn’t mention anything about code to include this interface, or anything around adding it to brx.d.ts. Is there something needed for the user to do, or is this irrelevant?
Second issue is that the explanation video (4.17 Exercise 6) says (at 38 seconds in) “…already added the Reference SPA Content component, however it’s not rendering…”.
This component is not mentioned prior to this? It’s not one of the available components either? Does the user need to do something to make it available?
The third issue is that the explanation video (4.17 Exercise 6) from 1:10 onwards, shows a file (components/Content/)“Content.tsx” being edited. This is not FAQContent.tsx (or the original ContentPage.tsx that the tutorial specifies to create FAQContent from) as specified in step 3 that’s being followed, although the code looks the same?
It feels like there could be some missing instructions around where the FAQContent component comes from/becomes available on an FAQ detail page?
The rendering of the FAQ document doesn’t seem possible by following the steps in the tutorial as it currently is.
It seems that things can be made to work by editing the “faq (page)” layout that the course requires you to create and ensuring the name of the “FaqContent” Static component that is added is actually named “FAQContent” (note the case).
This looks like it probably works as that’s what the naming of the folder/component is, if you follow the instructions in 4.16 Exercise 6 -Step 3.
I’m guessing, although I’ve not tried, that you possibly could make things work with a static component named “FaqContent” in the “faq (page)” layout if you do some aliasing(?) in the components/App.tsx file, as was done for “FaqComponent” along the lines of:
You are correct. The mapping object maps the name of the incoming component object to a React class to invoke. Am I correct in understanding you are no longer blocked by this in your training?
I am running through the training materials to resolve this for future trainees, would like to thank you again for raising the issue.
Am I correct in understanding you are no longer blocked by this in your training?
That’s right. Having managed to figure out the details I’ve added in my last post, I was able to make it to the end of the developer foundations course.