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

Adding v2 of catalog-based get_content_metadata endpoint #983

Open
wants to merge 23 commits into
base: master
Choose a base branch
from

Conversation

pmakwana93
Copy link
Contributor

Adding v2 of catalog-based get_content_metadata endpoint

JIRA: https://2u-internal.atlassian.net/browse/ENT-9406

Post-review

  • Squash commits into discrete sets of changes
  • Ensure that once the changes have been deployed to stage, prod is manually deployed

Copy link
Contributor

@iloveagent57 iloveagent57 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking good. One suggestion to add a test case or two, after that I think it'll be ready to go.

'key': 'course-v1:edX+course+run2',
'status': 'published',
'is_enrollable': True,
'is_marketable': True,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: just to make the data more prod-like, could we try setting is_marketable: False?

},
)
@ddt.unpack
def test_get_content_metadata(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding one or maybe two more test cases where no content keys filter is passed in the GET request, and the catalog query either allows or does not allow a restricted run.

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

Successfully merging this pull request may close these issues.

2 participants