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

Event date facet (DDFFORM-67) #918

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

Event date facet (DDFFORM-67) #918

wants to merge 4 commits into from

Conversation

kasperg
Copy link
Contributor

@kasperg kasperg commented Mar 22, 2024

Link to issue

https://reload.atlassian.net/browse/DDFFORM-67

Description

This PR adds support for filtering events by date. The PR consists of:

  • A new facet based on event dates
  • Rendering this facet as a date range component from the design system
  • Updating the facet to support AJAX loading like it is used for other facets in this view.

Please go through the individual commits for additional commentary.

Screenshot of the result

billede

Additional comments or questions

This PR depends on the related changes in the design system: danskernesdigitalebibliotek/dpl-design-system#562

Internal libraries go at the top alphabetically, internal at the
bottom.
kasperg added 3 commits March 22, 2024 08:49
Add a date facet and the facet date range module.

Render the new date facet on the event list and use the design
system to enhance it with a date range element.
For this to work we have to provide our own behavior which in turn
can use JavaScript from the design system.

Unfortunately this also requires a bunch of patches.
Load the translation and pass the proper configuration to Flatpickr.
@github-actions github-actions bot temporarily deployed to pr-918 March 22, 2024 07:51 Destroyed
@kasperg kasperg marked this pull request as ready for review March 22, 2024 07:56
Copy link
Contributor

@LasseStaus LasseStaus left a comment

Choose a reason for hiding this comment

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

I think there are some issues with this.

Since most of this logic comes from the design system, i will add most of my thoughts in the design system.

So some things i have tested here in the cms, will be highlighted in the design PR with suggestions.

Two things for the cms tho:

  • If i select a date range, and reload the page, the css dosn't gets rendered for me.
  • If i select a date range that contains 0 results, the rest of the filters goes away. I guess this is default behaviour with the current setup, but if we could keep them visible instead of them disappearing i think that would be a plus. ➕

Base automatically changed from event-facets to release/form-sprint-9 March 22, 2024 14:44
Base automatically changed from release/form-sprint-9 to develop April 2, 2024 12:47
@kasperg kasperg changed the base branch from develop to release/form-sprint-10 April 2, 2024 12:52
Base automatically changed from release/form-sprint-10 to develop April 8, 2024 14:17
@kasperg kasperg changed the base branch from develop to release/hermod-sprint-12 April 16, 2024 07:53
Base automatically changed from release/hermod-sprint-12 to develop April 23, 2024 08:34
@kasperg kasperg changed the base branch from develop to release/hermod-14 April 30, 2024 18:15
Base automatically changed from release/hermod-14 to develop May 2, 2024 14:52
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