Searched hist:ee9dbf1506bc8a2e17701b4e3c1bc1caf77e1561 (Results 1 – 5 of 5) sorted by relevance
| /plugin/annotations/ |
| H A D | plugin.info.txt | ee9dbf1506bc8a2e17701b4e3c1bc1caf77e1561 Wed Jun 03 05:12:45 UTC 2026 tracker-user <82045103+tracker-user@users.noreply.github.com> Add nested reply threading; sync docs
Replies can now be threaded under one another instead of only sitting
flat under their annotation.
Backend:
- helper.php: addReply() takes an optional parentId, stored on each reply
after sanitising it to hex; an empty or unknown parent simply falls back
to a top-level reply. Replies remain a flat list, with the parent link
carried as data.
- action.php: the reply action forwards parentId and returns the full
updated annotation (not just the new reply) so the client re-renders the
whole thread in one round-trip. Also fix a stray-indented docblock and
drop the inaccurate "and exit" wording on the JSON responders.
Docs / manifest:
- DESIGN.md: document the parentId field, the flat-storage-plus-client-tree
model, and the full-annotation reply response.
- README.md: note that replies can nest.
- plugin.info.txt: bump the date.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
| H A D | DESIGN.md | ee9dbf1506bc8a2e17701b4e3c1bc1caf77e1561 Wed Jun 03 05:12:45 UTC 2026 tracker-user <82045103+tracker-user@users.noreply.github.com> Add nested reply threading; sync docs
Replies can now be threaded under one another instead of only sitting
flat under their annotation.
Backend:
- helper.php: addReply() takes an optional parentId, stored on each reply
after sanitising it to hex; an empty or unknown parent simply falls back
to a top-level reply. Replies remain a flat list, with the parent link
carried as data.
- action.php: the reply action forwards parentId and returns the full
updated annotation (not just the new reply) so the client re-renders the
whole thread in one round-trip. Also fix a stray-indented docblock and
drop the inaccurate "and exit" wording on the JSON responders.
Docs / manifest:
- DESIGN.md: document the parentId field, the flat-storage-plus-client-tree
model, and the full-annotation reply response.
- README.md: note that replies can nest.
- plugin.info.txt: bump the date.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
| H A D | README.md | ee9dbf1506bc8a2e17701b4e3c1bc1caf77e1561 Wed Jun 03 05:12:45 UTC 2026 tracker-user <82045103+tracker-user@users.noreply.github.com> Add nested reply threading; sync docs
Replies can now be threaded under one another instead of only sitting
flat under their annotation.
Backend:
- helper.php: addReply() takes an optional parentId, stored on each reply
after sanitising it to hex; an empty or unknown parent simply falls back
to a top-level reply. Replies remain a flat list, with the parent link
carried as data.
- action.php: the reply action forwards parentId and returns the full
updated annotation (not just the new reply) so the client re-renders the
whole thread in one round-trip. Also fix a stray-indented docblock and
drop the inaccurate "and exit" wording on the JSON responders.
Docs / manifest:
- DESIGN.md: document the parentId field, the flat-storage-plus-client-tree
model, and the full-annotation reply response.
- README.md: note that replies can nest.
- plugin.info.txt: bump the date.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
| H A D | action.php | ee9dbf1506bc8a2e17701b4e3c1bc1caf77e1561 Wed Jun 03 05:12:45 UTC 2026 tracker-user <82045103+tracker-user@users.noreply.github.com> Add nested reply threading; sync docs
Replies can now be threaded under one another instead of only sitting
flat under their annotation.
Backend:
- helper.php: addReply() takes an optional parentId, stored on each reply
after sanitising it to hex; an empty or unknown parent simply falls back
to a top-level reply. Replies remain a flat list, with the parent link
carried as data.
- action.php: the reply action forwards parentId and returns the full
updated annotation (not just the new reply) so the client re-renders the
whole thread in one round-trip. Also fix a stray-indented docblock and
drop the inaccurate "and exit" wording on the JSON responders.
Docs / manifest:
- DESIGN.md: document the parentId field, the flat-storage-plus-client-tree
model, and the full-annotation reply response.
- README.md: note that replies can nest.
- plugin.info.txt: bump the date.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
| H A D | helper.php | ee9dbf1506bc8a2e17701b4e3c1bc1caf77e1561 Wed Jun 03 05:12:45 UTC 2026 tracker-user <82045103+tracker-user@users.noreply.github.com> Add nested reply threading; sync docs
Replies can now be threaded under one another instead of only sitting
flat under their annotation.
Backend:
- helper.php: addReply() takes an optional parentId, stored on each reply
after sanitising it to hex; an empty or unknown parent simply falls back
to a top-level reply. Replies remain a flat list, with the parent link
carried as data.
- action.php: the reply action forwards parentId and returns the full
updated annotation (not just the new reply) so the client re-renders the
whole thread in one round-trip. Also fix a stray-indented docblock and
drop the inaccurate "and exit" wording on the JSON responders.
Docs / manifest:
- DESIGN.md: document the parentId field, the flat-storage-plus-client-tree
model, and the full-annotation reply response.
- README.md: note that replies can nest.
- plugin.info.txt: bump the date.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|