Recognize aliases when resolving inherited icons

[vanto]

Idea
Currently, inherited page icons only work for the exact page reference. It would be nice if this plugin would also take aliases into account until logseq/logseq#3763 might be solved.

[yoyurec]

check latest update!

[vanto]

Thanks for the prompt response. It does not do what I expected, maybe I didn't put it precisely. Here is my scenario:

People.md

icon:: 👤

Elon Musk.md

page-type:: [[People]]
alias:: Elon

When I now write something like, only Elon Musk get the icon but not Elon.
Lorem ipsum dolor sit [[Elon Musk]], consectetur adipiscing elit. Ut ex dui, elementum et [[Elon]] in, pretium elementum odio. Phasellus rhoncus rutrum justo sed malesuada.

Thanks, HTH

[yoyurec]

oh, i thought you have:

People.md

icon:: 👤
alias:: ppl

Elon Musk.md

page-type:: [[ppl]]

[yoyurec]

will try...

[yoyurec]

should be something like:

• try icon from page
• if not, try to go page alias to original page and take its icon
• if not, try to take inherited from props page icon
• if not, try to take inherited from props, if it's alias, go to original page and take its icon

[yoyurec]

uhhh.... it was challenging )))
check latest release!

• original page
• aliased page
• original page with inherited props-as-page
• aliased page with inherited props-as-page
• original page with inherited props-as-alias

+ cases when local icon wins inherited )))

PS: aliased page with inherited props-as-alias not covered yet, cose to complex rare case with possible performance issues

check latest update!

[vanto]

Awesome, this works! Thanks for the fast implementation.

[yoyurec]

i'm not so much using aliases.... so case "original page with inherited props-as-alias" (which i've implemented first, wrongly) - maybe delete it? isn't it rare?
b'cose EACH link checks 4 times (( but can be 3 )))

[vanto]

Is this the scenario from #1 (comment)? I would not need that. I, too, think it is a rather rare use case.