The extension will try to find any items that contain that full UID, which is good for root module pages. But, the logic around periods (.) will try to also find items that contain learn.azure in this case. That is going to be way too many items. In fact, it fails to load.
The number of work items returned exceeds the size limit of 20000. Change the query to return fewer items.
We don't currently look for root module UIDs for special behavior, but maybe we should. And then, for those root module UIDs, we should probably not try sub-parsing the UID. It's possible we can do this via URL, where modules shouldn't have anything beyond the module name in the URL (excluding query and fragment portions): just /learn/modules/{module-name}/.
In an overreach from fixing #73, the queries now can include too many results, based on the initial UID it is parsing.
For example, a root module page: https://docs.microsoft.com/en-us/learn/modules/azure-storage-fundamentals/ UID:
learn.azure.azure-storage-fundamentals
The extension will try to find any items that contain that full UID, which is good for root module pages. But, the logic around periods (
.
) will try to also find items that containlearn.azure
in this case. That is going to be way too many items. In fact, it fails to load.We don't currently look for root module UIDs for special behavior, but maybe we should. And then, for those root module UIDs, we should probably not try sub-parsing the UID. It's possible we can do this via URL, where modules shouldn't have anything beyond the module name in the URL (excluding query and fragment portions): just
/learn/modules/{module-name}/
.