feat: add has_course_author_access to CourseHomeMetadataView response [BB-9082]

[0x29a]

Description

Adds has_course_author_access boolean to CourseHomeMetadataView. Currently it's used to control visibility of the "View as Staff" button here: openedx/frontend-app-learning#1436

Testing

Open any unit in frontend-app-learning, open Network tab in your browser console, and search for meta there. There will be a single request, and its JSON response should contain has_course_author_access key. It should be False for all users that don't have access to Studio, especially those having the "Limited Staff" course team role.

[openedx-webhooks]

Thanks for the pull request, @0x29a!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/wg-maintenance-edx-platform. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[kaustavb12]

Perhaps add some tests here to make sure the correct value for has_course_author_access for full staff/limited staff roles

[kaustavb12]

@0x29a Left a couple of small comments, but otherwise the changes looks good.

👍

• I tested this: Tested in local devstack
• I read through the code

[itsjeyd]

OSPR management note: User-facing change, so will likely need product approval before we can move forward with engineering review and merge.

Marking as blocked for now.

CC @mphilbrick211

[itsjeyd]

OSPR management note: Product review complete, see openedx/platform-roadmap#361 (comment).

[farhaanbukhsh]

@0x29a Can you please rebase the PR?

[0x29a]

@farhaanbukhsh, done.

[farhaanbukhsh]

@0x29a Thank you for the work here I have tested this and all works well I have add few nit picks once done we will be in a good place to merge this.

[farhaanbukhsh]

Suggested change

	return has_studio_write_access(user, course_key, service_variant)
	return has_studio_write_access(user, course_key, service_variant=service_variant)

[farhaanbukhsh]

👍

• ✅ I tested this on Tutor devstack and check the testcases.
• ✅ I read through the code
• ❌ I checked for accessibility issues
• ✅ Includes documentation
• ❌ I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.