Skip to content

Changelog ​

Documented against packages at 2.0.2. Packagist badges on the overview always show the latest published version.

2.0.2 ​

UI and backend polish shared by Blade Comments and Livewire Comments:

  • GitHub-style layout — comment threads, composer toolbar, and action chrome aligned across both UIs.
  • Full emoji picker — composer insert and reaction picker; not limited to the six quick types.
  • Reactions API — accepts any Unicode emoji / ZWJ sequence as type, max 32 characters. config('vgcomment.reaction_types') is only a quick-suggestion list for the UI.
  • Nested replies — replies load by root_id, then Comment::nestReplies() builds a parent_id tree for deep indentation.
  • Upload paths
    • Paperclip → file attached as chips (sent with the comment, shown under the post).
    • Insert image / paste / drag-drop → upload then insert Markdown ![alt](url) into the content.
  • Markdown — bold/italic toolbar helpers; server-side soft normalization so markers like **bold ** still render as emphasis (code spans left alone).
  • Blade inline reply — Reply opens a composer under that comment (primary UX); top banner remains a secondary signal.

2.0.x line ​

  • Laravel ^10|^11|^12|^13, PHP ^8.2
  • Blade UI recommended; Livewire UI requires Livewire ^4.0
  • Shared vigstudio/vgcomments core (REST, admin, validation)

1.x ​

Still on Packagist for existing apps. Prefer 2.0 for new projects.

MIT · Blade-first for 2.x · Livewire 4 supported