This is a brute force approach to support "context blocks" without taking any steps backwards (i.e., it supports older transactions and newer, modular transactions), but it feels like this is a lot of steps sideways and this change would be far better if it took a nuanced approach through T12921.

• T12921 is adjacent to mail rendering.
• T13439 mentioned the hovercard summary text.

D21574 implements the hovercard and summary length changes.

I think (?) this was pretty much resolved by the last round of changes. See T13291 for some followups.

PHI1224 describes a somewhat-adjacent situation: an install would like a way for external automated tooling to reference source files and generate editor links for them.

I don't currently plan to do this. At a bare minimum, T5474 may moot it.

This is also extremely silly, but I sometimes do it because I'm dumb and have muscle-memory for ⌘+1+⇥+⌘+V+⏎: searching for an object URL doesn't jump you to that object URL, but you probably meant to put it in the other box.

Yeah, if you know what information you want.

Tasks, projects, owners packages.

Pick three and I'll spruce them up today/tomorrow.

I'd just redo them on a case by case basic. Too many variables.

@chad, a lot of this is probably ultimately design -- how much passion do you feel for hovercards? The infrastructure is in good shape and I can add the "context hint" piece pretty easily if we want to look at that. Not sure if this is a bigger/more complicated project that you don't want to touch for the moment or whatever, though.

Per the latest update in D17502, this remains involved.

This actually seems a little difficult to fix...maybe just make it truncate with an ellipsis?

heh nice. And I didn't even have to cheat by using U+00A0.

@20after4 😆

One hovercard related suggestion in T10187: hard to understand status of sub-tasks from parent was to add projects/columns to Hovercards so that when mousing over subtasks you can see what projects they are in without opening them all. It looks like the latest mock has that so

These now show hovercards, which will show project information after M1455 is implemented. I'm just going to close this in favor of T10054, which is an umbrella task tracking related work.

These seem alright, I haven't been bothered by them.

👍 to @cspeckmim

We have a number of repositories (~20, though around 5 are generally active at a time) - what do you think about having the associated repository indicated somewhere on the revision hovercard?

See T5403 into T7858. I don't think this makes sense after T4100 with "Browse" UIs. All requests for this are "distinguish between multiple similarly-named projects", which is better done via "Browse".

The original request here seems to be for specific links to members and workboards from hovercards. I think it predates modern defaulting rules (i.e., clicking the tag now takes you to workboards for projects where they're in use) and we haven't seen other requests for this. I expect work adjacent to T10054 to continue giving us better behavior for clicking through. I don't understand the use case for frequently needing to access members quickly. I don't currently anticipate adding these links to hovercards.

D12692 is nearly the correct patch for this (and will support mentions, file embeds, etc., although currently not Fixes http://example.com/T123, which is parsed somewhat separately -- but that is also fixable fairly easily), it just has some tricky regex/execution order stuff that hasn't quite been sorted out.

We should make sure to include mentions support too.

thx for deduping

I'm just going to merge this into T3278 since I think that covers this completely.

That would be the summary Remarkup engine.

Then may I suggest somehow stripping away the [[ and the urls and only display the links text instead? Just an idea to not have it so cluttery at least, until (if in the future) there will be rendering of stuff there.

This is the expected behavior currently (not rendering out full Remarkup) and blocked on that we don't currently have a good "summary" type Remarkup target (which would be used say in task headers, chat summarys, hovercards, etc) where we only render a subset of Remarkup.