posit-dev / posit-dev/connect-extensions
Usage: accept same search terms as content list search
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 10
- Forks
- 8
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 1
Description
I was trying to answer a question about whether a certain group of apps were "important" or not. I could identify them through the search on the /connect/#/content/listing page in Connect, but then I couldn't filter to the same subset of content in the usage app. It would be nice if the filtering logic worked the same. (I realize this may require an API change in Connect.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the filtering behavior on /connect/#/content/listing with the usage app's current filters, then trace where each receives its search terms. Check whether the Connect API exposes the same filtering inputs. Done means the usage view can select the same subset of content as the content listing search.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100