Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidate get_usage_shiny() and get_usage_static() into get_views() #252

Open
nealrichardson opened this issue Apr 26, 2024 · 3 comments
Assignees

Comments

@nealrichardson
Copy link
Collaborator

Following the model of posit-dev/posit-sdk-py#170, conceal from the user the fact that there are different REST APIs for different content types and just present a single way to get usage stats for all types.

@jonkeane
Copy link
Contributor

This is the same as #218 yeah?

@nealrichardson
Copy link
Collaborator Author

Yep looks like it

@kmasiello
Copy link

kmasiello commented Apr 26, 2024

Consolidating some comments from a separate slack thread...

let's seek to return one usage data frame, regardless of content type, but keep a consistent and predictable column schema. If the content type does not have relevant data, keep the column in the output but return NA.

Suggesting "usage" over "views" because the latter isn't descriptive of programmatic access to APIs or pin reads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants