Tomasz Kowalczyk

@MrPetovan Your reasoning here and in #38 is correct, the `RegularParser::value()` method matches only "strings", ie. "not tokens" as parameter values. Mentioned URL contains shortcode token "closing mark", ie. forward...

@MrPetovan please look at #66. Please install the `dev-` composer version from the PR branch and verify that it works for your test cases. I added a quite thorough test...

Yes, this is one of the use cases for `Events::REPLACE_SHORTCODES`. Here is a quick example I wrote for you, I hope I understood your problem correctly: - create handlers with...

BTW The idea of an event before `Events::REPLACE_SHORTCODES` which allows you to tweak the replacement seems like a good idea. It may be a quite significant performance hit, but as...

@MrPetovan I'm sorry but I won't be able to continue work on this PR for now. You can try disabling self-closing tags by removing the part handling them in `RegularParser::shortcode()`...

@MrPetovan Yes, this project is very stable and I'm committed to maintaining it. It's just a temporary state where I won't have any time for side projects right now. I'm...

Hi @MrPetovan and @Fedcomp, I'd like to revive this PR as I think I've found a way to make both sides happy. I implemented a WIP commit [here](https://github.com/thunderer/Shortcode/pull/66/commits/9351dfaa2540f286e4cddef16cc22b3c98089922). The idea...

@MrPetovan I just tagged `v0.7.0` with all the improvements and fixes from #72. Did you have the chance to test this PR with your data? Let's give Friendica users the...

@MrPetovan what is the current status of shortcodes in Friendica? Will you be able to use the library now?

@rhukster these are all great ideas, let me explain how they could be achieved: 1. shortcodes without handlers are not processed (they are returned verbatim), but their content may be...