Skip to content

feat: allow filtering library by publish status - #1570

Merged
ChrisChV merged 17 commits into
openedx:masterfrom
open-craft:dvz/filter-by-published
Feb 5, 2025
Merged

feat: allow filtering library by publish status#1570
ChrisChV merged 17 commits into
openedx:masterfrom
open-craft:dvz/filter-by-published

Conversation

@DanielVZ96

Copy link
Copy Markdown
Contributor

Description

Adds a filter widget:

image

And an "Unpublished changes" badge:

image

Supporting information

Testing instructions

First pull the following branch: openedx/openedx-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

openedx-webhooks commented Dec 13, 2024

Copy link
Copy Markdown

Thanks for the pull request, @DanielVZ96!

This repository is currently maintained by @openedx/2u-tnl.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are 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.

Details

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.

@codecov

codecov Bot commented Dec 14, 2024

Copy link
Copy Markdown

Codecov Report

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

Project coverage is 93.24%. Comparing base (31f39cb) to head (a338fe8).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
src/search-manager/FilterByPublished.tsx 94.28% 2 Missing ⚠️
src/search-manager/data/apiHooks.ts 50.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1570   +/-   ##
=======================================
  Coverage   93.24%   93.24%           
=======================================
  Files        1100     1101    +1     
  Lines       21803    21859   +56     
  Branches     4632     4644   +12     
=======================================
+ Hits        20330    20383   +53     
- Misses       1408     1411    +3     
  Partials       65       65           

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

@pomegranited pomegranited left a comment

Copy link
Copy Markdown
Contributor

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?

</div>
<Highlight text={description} />
<Highlight text={description} /><br />
{props.hasUnpublishedChanges ? <Badge variant="warning">Unpublished changes</Badge> : null}

Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@jmakowski1123 @lizc577 @sdaitzman @marcotuts any comments on this? ^

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@jmakowski1123 @lizc577 @sdaitzman @marcotuts gentle nudge on this since we're blocked waiting for a decision here.

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

Copy link
Copy Markdown
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
Copy Markdown
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.)

@jmakowski1123

Copy link
Copy Markdown

I'd go with force-suggesting the "only published" filter.

@sdaitzman

Copy link
Copy Markdown

Agreed! Also adding, I do think Publish Status drop-down label should reveal when some filters are selected, like the Type and Tags do

@DanielVZ96

Copy link
Copy Markdown
Contributor Author

@pomegranited @jmakowski1123 @sdaitzman

I made it so that the two filters that display content are auto selected when ordering by recently published, and also disabled the other filter since it wouldn't show anything even when selected. I also added the badges that show the selected filters.

image

Comment thread src/search-manager/SearchManager.ts Outdated
const [searchKeywords, setSearchKeywords] = React.useState('');
const [blockTypesFilter, setBlockTypesFilter] = React.useState<string[]>([]);
const [problemTypesFilter, setProblemTypesFilter] = React.useState<string[]>([]);
const [publishStatusFilter, setPublishStatusFilter] = React.useState<PublishStatus[]>([]);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

When you resolve the conflicts for this file, please note that all of the search state variables are now managed as URL parameters, so this status should be too. Should look something like this:

  const [publishStatusFilter, setPublishStatusFilter] = useStateOrUrlSearchParam<PublishStatus>(
    [],
    'published',
    (value: string) => Object.values(PublishStatus).find((enumValue) => value === enumValue),
    (value: PublishStatus) => value.toString(),
    skipUrlUpdate,
  );

References:

@pomegranited pomegranited left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hi @DanielVZ96 , this looks great :) But I found a couple of bugs, could you take another look?

)}
</ActionRow>
)}
hasUnpublishedChanges={modified >= (lastPublished ?? 0)}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: Why not pull this from the added published_status field? I'm ok either way, but it seems like we shouldn't duplicate functionality here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

ohh nice catch

<SearchKeywordsField className="mr-3" />
<FilterByTags />
{!insideCollections && <FilterByBlockType />}
<FilterByPublished />

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could you please add <FilterByPublished /> to the LibraryCollectionPage too?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

will do

}
}, [searchSortOrder]);

const toggleFilterMode = React.useCallback((mode: PublishStatus) => {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Bug: Selecting one publish_status filter clears all the others? Maybe see FilterByBlockType for how its checkbox onChange handler works.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

it was because I forgot to add the setter to the dependencies. this was somehow breaking the tags filter tests so thank you so much for finding this :)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thank you for working out a simple fix! it's working great now.

@pomegranited pomegranited left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

👍 This looks and works great @DanielVZ96 , thank you for accommodating my suggestions and the UI tweaks from Product!

  • I tested this using the PR test instructions, plus tested using these filters on the Collection page.
  • I read through the code
  • I checked for accessibility issues by using my keyboard to navigate
  • Includes documentation N/A
  • User-facing strings are extracted for translation

@ChrisChV
ChrisChV merged commit 05dddce into openedx:master Feb 5, 2025
Arpit-Nakrani-Networked pushed a commit to Arpit-Nakrani-Networked/frontend-app-authoring that referenced this pull request Jul 13, 2025
…edx#1570)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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

Archived in project

Development

Successfully merging this pull request may close these issues.

7 participants