All tasks in the catalog are aligned to the authoring recommendations.
Most tasks are not.
It is not surprising that deep and shallow scan show different results. Shallow scan only looks at column names. Deep scan looks at a sample of the data. I've even noticed that two different runs of deep scan show different results as sample rows are different. This is the challenge with not scanning all of the data. Its a trade-off between performance/cost and accuracy. There is no right answer.
Need to add logic to batch these api requests and combine the result - https://github.com/vinaygaba/JetpackCompose.app/blob/master/gatsby-node.js#L68
Add a description, image, and links to the catalog topic page so that developers can more easily learn about it.
To associate your repository with the catalog topic, visit your repo's landing page and select "manage topics."
The Story display panel at the bottom of the screen has some alignment issues in one of the corners:
We should fix this so the lines align.