Each time the user accesses a content object fetch is called, this leads to a very noticeable delay in loading. I don't think we need to load it each time as apiCollection has already called fetch and the collection is there.
I've removed the content.fetch from the render function and all is working/loading expected, not sure if it has been added in for a very specific use case?
(It's recently been changed to try/catch but I think the fetch call can be removed)
Expected behaviour
No response
Steps to reproduce
Create a course, the more components you add the longer the delay when switching between content objects.
What happened?
Each time the user accesses a content object fetch is called, this leads to a very noticeable delay in loading. I don't think we need to load it each time as apiCollection has already called fetch and the collection is there.
I've removed the content.fetch from the render function and all is working/loading expected, not sure if it has been added in for a very specific use case?
(It's recently been changed to try/catch but I think the fetch call can be removed)
Expected behaviour
No response
Steps to reproduce
Create a course, the more components you add the longer the delay when switching between content objects.
Authoring tool version
rc4
Framework version
No response
What browsers are you seeing the problem on?
Firefox
Relevant log output
No response