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.

Sign up for GitHub

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

Jump to bottom

pepdb Migration #44

Closed
13 tasks done
nleroy917 opened this issue Jul 13, 2022 · 0 comments
Closed
13 tasks done

pepdb Migration #44

nleroy917 opened this issue Jul 13, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@nleroy917
Copy link
Member

nleroy917 commented Jul 13, 2022 •
edited
Loading

I need a place to keep track of endpoints that are working with the new PepAgent class.

PEP:

  • /pep/view

Namespace:

  • /pep/{namespace}
  • /pep/{namespace}/view
  • /pep/{namespace}/projects

Project:

  • /pep/{namespace}/{project}
  • /pep/{namespace}/{project}/view
  • /pep/{namespace}/{project}/zip
  • /pep/{namespace}/{project}/config
  • /pep/{namespace}/{project}/samples
  • /pep/{namespace}/{project}/samples/{sample_name}
  • /pep/{namespace}/{project}/samples/{sample_name}/view
  • /pep/{namespace}/{project}/subsamples
  • /pep/{namespace}/{project}/convert

Eido:
Complete

The PepAgent class is nice and mature for the project level data, bet less to for metadata about PEPs and then for namespaces.
@nleroy917 nleroy917 added the enhancement New feature or request label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nleroy917