Open nima opened 1 year ago
The point of this change is to allow a further configuration option where user can decide what the rendered text would look like. For example:
Where previously, the two following settings options would render into the third:
pkg:([-\w]+)
https://code.com.com/packages/$1
pkg:$1
Now you can decide what the rendered text should look like, and what parts of that are active; i.e., three options (rather than two), the third defining both the full rendered text, and what part of it is clickable (between braces):
[CompanyCode:{$1}]
pkg:GoldenAxe
Additionally you can add emojis to the linked (or unlinked) rendered html element.
I have to write more tests for this, I've discovered some edge cases that don't render correctly.
The point of this change is to allow a further configuration option where user can decide what the rendered text would look like. For example:
Where previously, the two following settings options would render into the third:
pkg:([-\w]+)
,https://code.com.com/packages/$1
⇨pkg:$1
Now you can decide what the rendered text should look like, and what parts of that are active; i.e., three options (rather than two), the third defining both the full rendered text, and what part of it is clickable (between braces):
pkg:([-\w]+)
,https://code.com.com/packages/$1
,[CompanyCode:{$1}]
⇨[CompanyCode:{$1}]
pkg:GoldenAxe
⇨ [CompanyCode:GoldenAxe]; bold here implies linked.Additionally you can add emojis to the linked (or unlinked) rendered html element.