WIP wiring up new content search API

[nealrichardson]

No description provided.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
548	511	93%	80%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
src/posit/connect/content.py	97%	🟢
src/posit/connect/paginator.py	100%	🟢
TOTAL	98%	🟢

updated for commit: 08a101f by action🐍

[Lytol]

PR is ready for adding the total to the content search results. Also, one observation on the draft PR, you can use the include=owner param to return the user object for the owner with each content item. This is super useful for avoiding n+1 scenarios and is probably worth supporting.

[nealrichardson]

PR is ready for adding the total to the content search results. Also, one observation on the draft PR, you can use the include=owner param to return the user object for the owner with each content item. This is super useful for avoiding n+1 scenarios and is probably worth supporting.

I don't quite follow but please push whatever you think useful to the branch. I'll otherwise wait until your PR lands and gets to radixu, sadly I don't have time to set up a local Connect environment.

[github-actions]

Hey there! 👋

We noticed that the title of your pull request doesn't follow the Conventional Commits specification. To ensure consistency, we kindly ask you to adjust the title accordingly.

Here are the details:

No release type found in pull request title "WIP wiring up new content search API". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - build
 - chore
 - ci
 - docs
 - feat
 - fix
 - perf
 - style
 - test