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

feat: the signatory is not mandatory on coursecertificate configurations #2515

Conversation

deborahgu
Copy link
Member

Credentials IDA requires signatories on ProgramCertificate configurations. However, on CourseCertificate configurations, not all sites will care if a signatory is present. The certificates themselves don't render in the credentials IDA, and this is cloned data from the system of record. Although this has always been nullable in the ORM because of the way django handles nullability for ManyToManyField, the django admin enforces the presence of a signatory.

This keeps the signatory required for ProgramCertificate, but makes it blankable for CourseCertificate.

FIXES: APER-3494

Run JavaScript tests locally with Karma

There is work being done on a fix to get Karma to run in CI. Until then, however, contributors are required to run these tests locally.

  • Make sure you are inside the devstack container
  • Run make test-karma
  • All tests pass

…ry on coursecertificates

Credentials IDA requires signatories on `ProgramCertificate`
configurations.  However, on `CourseCertificate` configurations,
not all sites will care  if a signatory is present. The
certificates themselves don't render in the credentials IDA,
and this is cloned data from the system of record. Although this has
always been nullable in the ORM because of the way django handles
nullability for `ManyToManyField`,  the django admin enforces the
presence of a signatory.

This keeps the  signatory required for `ProgramCertificate`, but makes
it blankable for `CourseCertificate`.

FIXES: APER-3494
@deborahgu deborahgu requested a review from a team as a code owner July 9, 2024 16:41
Co-authored-by: Jason Wesson <jsnwesson@gmail.com>
"""
a CourseCertificate configuration without a signatory passes validation
"""
expected = 302
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious as to why we expect a 302. Just a function of how the call works after saving an entry? A redirect to the list of course cert configs in Django admin?

Also, I know the method for saving is different than the Program cert test, but would it be easier/better to check that the admin form has no errors?

Copy link
Member Author

Choose a reason for hiding this comment

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

apparently saving successfully gives a redirect to the list page, I verified this is normal and expected in both reality and django tests.

@deborahgu deborahgu merged commit 66e6785 into master Jul 10, 2024
8 of 11 checks passed
@deborahgu deborahgu deleted the dkaplan1/APER-3494_credentials-has-a-coursecertificate-signatory-field-and-shouldnt branch July 10, 2024 14:33
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.

3 participants