For a while, we'll be in the situation that we have both assessments for the tree and assessments for the non-tree. The AnalysisWebWorker needs to call both of these assessors and combine the results into one result.
It also will need to build the tree somewhere at the top of the method. This can be done by calling the previously created buildTree function: https://github.com/Yoast/YoastSEO.js/issues/2028.
So the analyze method inside the AnalysisWebWorker needs to be changed so it calls two assessors: A normal Assessor and a TreeAssessor. Given that the method is already complex, we really want to abstract certain parts of it so it doesn't become unwieldy.
For a while, we'll be in the situation that we have both assessments for the tree and assessments for the non-tree. The
AnalysisWebWorkerneeds to call both of these assessors and combine the results into one result.It also will need to build the tree somewhere at the top of the method. This can be done by calling the previously created
buildTreefunction: https://github.com/Yoast/YoastSEO.js/issues/2028.So the
analyzemethod inside theAnalysisWebWorkerneeds to be changed so it calls two assessors: A normalAssessorand aTreeAssessor. Given that the method is already complex, we really want to abstract certain parts of it so it doesn't become unwieldy.