Skip to content

Conversation

@tvdeyen
Copy link
Member

@tvdeyen tvdeyen commented Feb 3, 2026

What is this pull request for?

Make the recently introduced public_on and public_until fields of elements usable by introducing UI to schedule element visibility.

Notable changes

Replaces the publish toggle with a split button which allows to schedule the element for publication.

Screenshots

CleanShot 2026-02-12 at 08 25 59@2x CleanShot 2026-02-12 at 08 25 19@2x CleanShot 2026-02-12 at 08 25 36@2x CleanShot 2026-02-12 at 08 25 11@2x

Checklist

  • I have followed Pull Request guidelines
  • I have added a detailed description into each commit message
  • I have added tests to cover this change

@tvdeyen tvdeyen self-assigned this Feb 3, 2026
@tvdeyen tvdeyen changed the title Element visibility button feat: Add schedule element button Feb 3, 2026
@tvdeyen tvdeyen force-pushed the element-visibility-button branch 6 times, most recently from c97a425 to f739f8e Compare February 10, 2026 13:25
@codecov
Copy link

codecov bot commented Feb 10, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.50%. Comparing base (28be7b8) to head (ce22641).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3621      +/-   ##
==========================================
+ Coverage   97.48%   97.50%   +0.01%     
==========================================
  Files         314      315       +1     
  Lines        8286     8332      +46     
==========================================
+ Hits         8078     8124      +46     
  Misses        208      208              

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@tvdeyen tvdeyen force-pushed the element-visibility-button branch from f739f8e to 9a59052 Compare February 11, 2026 13:04
Signed-off-by: Thomas von Deyen <vondeyen@blish.cloud>
If you want to have two buttons aligned under the
input fields of a form use the `.buttons` container
class
The hidden property hides an element from the
screen, but since the display property has
precedence we also need to force hide it visually.
Allows to programmatically clear flatpickr
@tvdeyen tvdeyen force-pushed the element-visibility-button branch 8 times, most recently from 601a4be to cc94e59 Compare February 12, 2026 07:50
@tvdeyen tvdeyen added this to the 8.2 milestone Feb 12, 2026
@tvdeyen tvdeyen marked this pull request as ready for review February 12, 2026 07:53
@tvdeyen tvdeyen requested a review from a team as a code owner February 12, 2026 07:53
@tvdeyen tvdeyen removed their assignment Feb 12, 2026
@tvdeyen tvdeyen force-pushed the element-visibility-button branch from cc94e59 to b7503f2 Compare February 12, 2026 16:10
@tvdeyen tvdeyen force-pushed the element-visibility-button branch 2 times, most recently from ce22641 to fefd7c5 Compare February 12, 2026 16:34
@tvdeyen tvdeyen force-pushed the element-visibility-button branch from fefd7c5 to 69008b5 Compare February 12, 2026 16:34
Easier to test time based publishing that way
Replaces the public toggle with a split button
which allows to schedule the element for publication.
No need to query the length here. Thanks rubocop
@tvdeyen tvdeyen force-pushed the element-visibility-button branch from 69008b5 to e22b73b Compare February 13, 2026 11:53
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.

1 participant