fix: course about URL should use course key, not course run key. #1171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the spent table was first implemented, it utilized the Analytics API to fetch enrollments, and that data source contained a course key field. However, when we switched over to real-time fetching of redemptions via the transaction list API for assignable budgets, we erroneously treated the
content_key
field as a course key, breaking the course about page link in the spent table.The following two PRs implment a
parent_content_key
field in the transaction list API, which we can now utilize for the real-time spent table implmentation:parent_content_key
to transaction when redeeming content enterprise-subsidy#209ENT-8389
For all changes
Only if submitting a visual change