Skip to content

DEV: Modernize the remaining of the post stream to Glimmer components #32653

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

Open
wants to merge 84 commits into
base: main
Choose a base branch
from

Conversation

megothss
Copy link
Contributor

@megothss megothss commented May 8, 2025

No description provided.

megothss added 30 commits May 8, 2025 17:11
Replaced the old scrolling post stream with a new `PostStream` Glimmer component when `useGlimmerPostStream` is enabled. Added conditional rendering for loading indicators and integrated the actions for post loading.

Loading more posts above and below is working, although the scroll tracking is not implemented yet.
The topic route template now checks which version of the PostStream is enabled in the settings and uses the correct component.
Replaced private method prefixes and streamlined debounce calls for improved clarity. Introduced private fields for better encapsulation and removed unused properties to reduce clutter. Adjusted SLACK_FACTOR and updated relevant calculations for more precise screen tracking.
Reorganized method placements, renamed a method for clarity, and corrected parameter usage in the `updateIntersectionObservers` function. These changes improve code readability and maintainability while preserving existing functionality.
Ensure methods properly handle cases where there are no visible posts. Prevents errors by adding null checks and skipping unnecessary observer updates. Improves resilience of post tracking logic during edge cases.
Introduce bottom eyeline tracking for improved scroll position monitoring for the posts in the bottom of the page in the post-stream component. Added a debug mode for visualizing the eyeline position, along with various cleanup and restructuring to support this feature. Updated event handling, intersection observers, and DOM manipulation accordingly.
Fixes an issue where the post observer was not properly re-attached when bottom eyeline tracking was disabled. Ensures the observer's state is correctly updated to avoid inconsistent behavior during scroll events.
Debugging `console.log` statements used for development purposes have been removed to clean up the code.
This change ensures touchmove events trigger the same scroll logic across devices, improving consistency in user interactions. The corresponding cleanup logic for touchmove was also added to ensure proper event listener removal.
Adjusted the scrollable area and progress calculation to handle scenarios where the viewport height exceeds the document height or results in a non-scrollable area. This ensures accurate progress tracking and prevents division by zero errors.
This commit introduces logic to enable bottom eyeline tracking only when the current post's height exceeds the viewport height. It also optimizes the scrolling tracking behavior by removing unnecessary debounce usage, improving performance and clarity. These changes ensure better handling of large posts and enhance user experience during scrolling.
This commit introduces a more robust system for eyeline tracking, ensuring proper handling when the current post height exceeds the viewport. The changes streamline debounce logic, improve observer interactions, and make the code more modular for maintainability.
Replaced `&&` with `||` to ensure the condition checks each boundary independently. This prevents incorrect behavior when only one of the boundaries changes.
Ensure the current post remains tracked only if it is visible on screen. Adds a check to confirm the current post is within on-screen boundaries, improving accuracy during scrolling.
Updated event listeners to use new handler methods `#postedTriggered` and `#scrollTriggered`. This improves readability and ensures consistent handling of post stream actions like jumping to posts and responding to refresh events.
Comment on lines 15 to 16
// TODO (glimmer-post-stream) remove this modifier.
// The Glimmer post stream applies the `sticky-avatar` class to all posts
Copy link
Member

Choose a reason for hiding this comment

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

Seems like sticky-avatar is now added statically in widgets/post.js, so I think we can drop this modifier right now?

megothss and others added 2 commits June 3, 2025 18:39
Co-authored-by: David Taylor <david@taylorhq.com>
Co-authored-by: David Taylor <david@taylorhq.com>
@megothss megothss requested a review from a team as a code owner June 3, 2025 23:30
@github-actions github-actions bot added chat PRs which include a change to Chat plugin i18n PRs which update English locale files or i18n related code migrations-tooling PR which includes changes to migrations tooling labels Jun 3, 2025
@megothss megothss force-pushed the dev/glimmer-post-stream-phase-2 branch from 4bcea41 to 52cbaab Compare June 3, 2025 23:40
@github-actions github-actions bot removed chat PRs which include a change to Chat plugin i18n PRs which update English locale files or i18n related code migrations-tooling PR which includes changes to migrations tooling labels Jun 3, 2025
megothss and others added 14 commits June 3, 2025 20:47
This update ensures the topic ID is passed and tracked in post-stream viewport-related modifiers. The implementation consumes tracked arguments to handle cleanup when their values change, improving stability and memory management. Additional clean-up steps for instance properties and collections have been added for robustness.
Update `preventCloak` API to support enabling/disabling cloaking for posts dynamically. Refactor `cloakingPrevented` structure to reset its state when the topic changes, ensuring cleanup on topic transitions
Replaced Symbol-based approach with a WeakMap to store post model references. This prevents memory leaks by ensuring references are automatically cleaned up when DOM elements are removed. Updated all relevant methods to use the new WeakMap implementation.
Refined comments and naming to enhance code clarity and maintainability. Fixed typographical errors and extended functionality in the intersection observer callback to better track eyeline position and update the visible post state effectively.
Co-authored-by: David Taylor <david@taylorhq.com>
The touchmove event listener was unnecessary as scrolling is already handled by the scroll event. This simplification reduces event registration overhead and improves code maintainability.
Introduce a new `@trackedArray` decorator to enable seamless integration with `TrackedArray`. Added comprehensive tests ensuring proper behavior, including initialization, setting, and tracking changes to arrays. This improves reactivity and ensures robust handling of array mutations.
Replace manual and legacy state management of `selectedPostIds` with `@trackedArray` for improved reactivity and performance. Simplifies the code by removing unnecessary `set` calls and ensures better integration with tracked properties.
This modifier is no longer necessary as the Glimmer and widget post stream now handles the application of the `sticky-avatar` class directly.

Cleanup includes deleting the modifier implementation and removing its usage in topic templates.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants