Threaded Conversations

[sirinath]

Is your feature request related to a problem? Please describe. I am looking to create threaded conversations and messages. These can have subject lines and custom fields like starts, rating, tags, etc.

Describe the solution you'd like Add the ability to create threads conversations. E.g.

• Reddit style source: https://www.reddit.com/r/Idris/comments/hs7eti/how_can_i_get_the_api_documentation_installed/
• Chat source: https://quasar.dev/vue-components/chat
• Feed Source: https://fomantic-ui.com/views/feed.html
• Comments Source: https://fomantic-ui.com/views/comment.html Source: https://commento.io/

Additional elements can perhaps be borrowed from:

• https://www.discourse.org/
• https://flarum.org/

[claviska]

This is a pretty broad suggestion. Most of these are compositions of smaller components, many of which are already possible using:

• Avatar
• Badge
• Button
• Icon
• Checkbox
• Textarea

I'm trying to avoid incorporating patterns like this because they're opinionated and hard to customize as an individual component. Feel free to break it up into smaller requests, though. 😄

[sirinath]

Items required to impliment this type of components:

• [ ] Container
  • [ ] Indentation or spacing padding block
  • [ ] Indentation padding block line
  • [ ] Depth, grouping and condition based styling
  • [ ] Marker and decided lines
  • [ ] Conditional styling
  • [ ] Borders
  • [ ] Grouping and nesting
  • [ ] Collapse / expand
  • [ ] Multi orientation
• [ ] Vote
  • [ ] Up vote
  • [ ] Downvote
  • [ ] Thums up
  • [ ] Thums down
  • [ ] Accepted
  • [ ] Voting icons
• [ ] Rating
  • [ ] Star
  • [ ] Score
  • [ ] 1 to n
  • [ ] Icons
• [ ] Flagged
  • [ ] Icons and
  • [ ] Styles
• [ ] Status
  • [ ] Icons and
  • [ ] Styles
• [ ] Message/alert types: Information, Warning, Error, etc.
  • [ ] Icons and
  • [ ] Styles
• [ ] Status/flag/message/alert based styling: Flagged, Information, Warning, Error, Accpeted, Rejected, Pending, Done, To do, etc.
  • [ ] Support style changes with state changes
  • [ ] Specify state related style
• [ ] Hieracial, multitype, multilevel, value included tags to support broad categories of tagging, taxonomies and folksonomies - e.g. news, programming:rust:1.44.1, functional-programming:scala, jvm-language:scala, metelogy:rust, dev:internals, resources:faq, etc,
• [ ] Reaction
  • [ ] Thums up
  • [ ] Thums down
  • [ ] Heart
  • [ ] Emoji
  • [ ] Accpepted
  • [ ] Rejected
• [ ] Avatar
• [ ] Badge
• [ ] Button
• [ ] Icon
• [ ] Checkbox
• [ ] Subject/Title/Headers
• [ ] Editable text items
  • [ ] Labels
  • [ ] Text areas
  • [ ] Nested quotations
• [ ] Textarea
  • [ ] Nested quotations
  • [ ] Baloon text
  • [ ] Above or below label - sanitisation, warning, information messages
  • [ ] Ritch text
  • [ ] MD
    • [ ] Display
    • [ ] Edit
  • [ ] AsciiDoc
    • [ ] Display
    • [ ] Edit
• [ ] Embbeded object
  • [ ] Media
  • [ ] Link
  • [ ] Social media
• [ ] Action menue
• [ ] Menue items
• [ ] Bookmark / favourite
• [ ] Sorting options/order menu/headers/buttons items/icons
• [ ] Conversational/hirerachial view, lines view, ____ view buttons/menue items/icons
• [ ] n minutes, days, week, moths, years, items, etc. ago text lables
• [ ] Receipts
  • [ ] Read receipts
  • [ ] Marks
  • [ ] Image
  • [ ] Sent receipts
  • [ ] Marks
  • [ ] Image
  • [ ] Resolution based adjustment - low resolution may not support image based receipts as it would be difficult to figure out so it should switch based on screen resolution
• [ ] Dashboads for stat summaries
• [ ] Updatable place holders which pull content when comes to edge of feed or when new items are added
• [ ] Updatable place holders list/feed/layout
• [ ] Card which supports
  • [ ] Profile which elegantly supports the following nested components
  • Avatar
  • Layout
  • Text
  • Headers
  • Buttons
  • [ ] Message header which elegantly supports the following nested components
  • Avatar
  • Layout
  • Text
  • Headers
  • Time lable
  • Menue

NB: As always it is good to have all the components atomic, which the user can create composite components as to their design. The atomic components can have their variation though.

[claviska]

Thanks for the breakdown. This is still very broad and many of these components have already been implemented (avatar, badge, button, icon, checkbox, rating). I'm more keen to focus on lower-level components that the majority of users will find helpful.

If there's a specific component you'd like to see, feel free to post a feature request for that individual component. The Reddit-style vote up/down would be a good candidate, for example.

Most everything else in the original screenshot is already possible with a combination of Shoelace components and custom markup. I'm not seeing anything else that jumps out as a generic component, though. 😄