latestchatty / chatty Goto Github PK

Then we can stop "collapsing" like the shack does, saving both CSS and render performance. This should reduce the number of watches quite a bit, and reduce the virtual DOM size.

Notify the user when a new post is loaded that was a reply to one of their posts.

Ex: shack highlights current user as blue.

When new replies arrive, they will shift the scroll of the page. This is disorienting and annoying.

In the ng1 chatty, I implemented a (hacky) fix that adjusted the page scroll as necessary to prevent any shifting. Something similar will have to be implemented in the ng2 version. It should be easier than it was in ng1 though. Use an attribute directive.

Find posts which have a post author equal to the logged in user.

Optionally allow setting/retrieving settings from cloud vs local storage.

Shack does a gradient based highlight (stateless). Various mobile platforms have other ways of indicating (stateful). Must decide...

With watch count in mind!

The PRL (post rate limiter) reduces the number of posts per minute you can make. Currently when it is hit, the post just disappears into the void. This should probably be more gracefully handled.

ShackBrowse has a "queue" that it keeps track of to post later after PRL comes back. This would be the ideal solution.

Currently any thread that has a reply to you in it, each new post will increment the indicator. Enhance this to only increment when the new post itself is the reply to you.

Allow creating new root post too, not just replies.

Despite being the same directive, the user name in expanded replies is not clickable to add a new tab.

Currently this requires 1 watch per comment. If this were simply a flat list with depth, it would be 1 watch per thread instead.

Should support viewing individual threads in tabs with a left-most tab of "All Threads". The little permalink in the top left of a post should create a new tab of that thread. Something like that anyway.

The article posts contain relative links which don't work.

Similar to the posts with green +N indicator, show when tabs have new replies in them.

Scrolling adjust when new replies come in above the current view.

No more superthreads with 600 replies ruining the already tiny scroll bar.

Large width/height gfycat videos only show the top left portion of the video. Tried the JS embed instead of iFrame but it didn't seem to work with dynamically loaded dom elements.

Reorder posts (except collapsed) by recent replies, similar to an F5 from the normal shack.

Angular 1.3.6 no longer searches nested objects, so filtering isn't working as expected any longer.

Make a special count method that excludes html tags so that colorful replies get rendered properly.

Currently they are part of the tab itself, which gets persisted in client data / local storage. Tabs should have a 'type' which gets a description from code.

$filter (used for the "search" box) no longer exists in ng2. Might have to custom implement something. Could be slightly challenging, given the post body is broken into pieces for embeds.

Should either clear the filter text box or re-filter after tab change.

A/Z for browsing up/down replies. Are there more?

Depends on #59.

Presumably TSLint can be used to manage the code style rules like ESLint was previously. Currently while there is a compile step, there isn't a lint step for style.

When a long thread is truncated and you click on a reply toward the bottom, the full view should be scrolled into view after it's rendered.

Currently:
-Regex based for matching urls
-Using excessively complex regex replace for embed urls
-Weird inconsistent embed behavior
-No unit tests

Ideally:
-Regex based for matching
-Url parsing for replacing
-More reusable embeds for iframes at least.
-Unit tests covering most/all scenarios to prevent regressions

Make a new route '/messages' where you can

• read shack messages
• ideally paged
• filter (angular style, locally anyway)
• delete messages
• respond / write messages

Posts should clearly display a banner for the various mod tags (nws, interesting, etc).

Depends on #55. Once filtering is available, the tab service can be finished/fixed. There are lots of TODO comments all over where tab service features are disabled as well.

Depends on #62.

When inside a oneline, it should hide it, and when inside a full post, it should be clickable.

When a new thread is available (+X next to reflow button), and that new thread has replies, those replies are included in the tab counts, but looking at the tab won't show this until a reflow is performed.

Gotta decide how to handle it (use tabs? inline? popup?)

any possibility of this happening?