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: allow filtering library by publish status #1570

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

Conversation

DanielVZ96
Copy link
Contributor

Description

Adds a filter widget:

image

And an "Unpublished changes" badge:

image

Supporting information

Testing instructions

First pull the following branch: openedx/edx-platform#36031

  1. [If needed] Create a new library with new components in http://apps.local.openedx.io:2001/course-authoring/libraries
  2. With the tutor stack running execute the following command: tutor dev exec cms bash -c './manage.py cms reindex_studio --experimental '
  3. Publish and edit some components. Take note of the number of components that have been published, published and modified after, and never been published
  4. Open the filter widget and assert that the numbers of each publish status corresponds to the number you wrote down in step 2
  5. Assert that filtering by each value only shows the correct components:
    • Published when the component was published and not modified since
    • Modified when the component has been modified after being published
    • Never when the component has never been published

Deadline

ASAP

Other information

Private-Ref

@DanielVZ96 DanielVZ96 requested a review from a team as a code owner December 13, 2024 22:03
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Dec 13, 2024
@openedx-webhooks
Copy link

Thanks for the pull request, @DanielVZ96!

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/2u-tnl. 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:

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.

Copy link

codecov bot commented Dec 14, 2024

Codecov Report

Attention: Patch coverage is 91.66667% with 3 lines in your changes missing coverage. Please review.

Project coverage is 92.96%. Comparing base (b110b6b) to head (6d3db8d).

Files with missing lines Patch % Lines
src/search-manager/FilterByPublished.tsx 91.30% 2 Missing ⚠️
src/search-manager/data/apiHooks.ts 50.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1570      +/-   ##
==========================================
- Coverage   92.96%   92.96%   -0.01%     
==========================================
  Files        1075     1076       +1     
  Lines       21190    21227      +37     
  Branches     4554     4565      +11     
==========================================
+ Hits        19700    19734      +34     
+ Misses       1424     1421       -3     
- Partials       66       72       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@pomegranited pomegranited left a comment

Choose a reason for hiding this comment

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

Hi @DanielVZ96 , this is working well! Left a few comments about extracting out user-facing strings, and some UI questions/issues. Let me know when it's ready for another review?

@@ -75,7 +79,8 @@ const BaseComponentCard = ({
<div className="text-truncate h3 mt-2">
<Highlight text={displayName} />
</div>
<Highlight text={description} />
<Highlight text={description} /><br />
{props.hasUnpublishedChanges ? <Badge variant="warning">Unpublished changes</Badge> : null}
Copy link
Contributor

Choose a reason for hiding this comment

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

Please extract "Unpublished changes" into a message so it can be translated.

return (
<SearchFilterWidget
appliedFilters={[]}
label="Publish Status"
Copy link
Contributor

Choose a reason for hiding this comment

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

Please extract "Publish Status" to a message so it can be translated.


const clearFilters = React.useCallback(() => {
setPublishStatusFilter([]);
}, []);
Copy link
Contributor

Choose a reason for hiding this comment

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

Selecting a Published Status filter doesn't show the "clear filters" link?

Need to modify canClearFilters.

onChange={() => { toggleFilterMode(PublishStatus.Published); }}
>
<div>
Published
Copy link
Contributor

Choose a reason for hiding this comment

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

Please extract these "Published", "Modified since publish", and "Never published" labels to messages so they can be translated.

@@ -163,6 +171,7 @@ export const SearchContextProvider: React.FC<{
searchKeywords,
Copy link
Contributor

Choose a reason for hiding this comment

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

Some UI questions, feel free to bounce these off the UX folks if you agree :)

  1. Currently, sorting by "Recently Published" also filters out any "Never published" items, but this is entirely hidden from the user.
    Should we make this explicit force-selecting the "Published" and "Modified since publish" filters in the UI?
  2. Should the Publish Status drop-down label reveal when some filters are selected, like the Type and Tags do?
    image
    To make the drop-down more concise, I'd use "Status: Published" or whatever instead of "Published status: Published".

>
<div>
Published
{' '}<Badge variant="light" pill>{publishStatus[PublishStatus.Published] ?? 0}</Badge>
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think you need to have this {' '} in there to separate the label from the Badge, do you? FilterByTags doesn't: https://github.com/open-craft/frontend-app-authoring/blob/dvz/filter-by-published/src/search-manager/FilterByTags.tsx#L66-L67

Copy link
Contributor

Choose a reason for hiding this comment

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

(And strictly speaking, the Badge should be part of the translated text so that RTL languages can put the count badge to the left of the text. But there's a number of places where we'd need to fix this, so it's ok if you don't do it here.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-source-contribution PR author is not from Axim or 2U
Projects
Status: Waiting on Author
Development

Successfully merging this pull request may close these issues.

4 participants