I've found a bug. When there's more than one share token (I've test it with 3) from differents components, the visit counter don't work properly. It only increments with one token and not for all.
I show en example with the following video:

I've created first of all, a token for a survey that works fine. Then I've created a second token on another component (blog) that works fine. But for the third token (on the first component, the survey) I've check that there's no response changing the counter visit for it and also occured the same the first token. The only counter that increases is the blog token

Hi @ivan-mr, thanks for the review!

The visit counter is not incrementing for those tokens because the components are published, thus not needing tokens to be accessed. Since the permissions resolve once the component is checked to be published, the share token is not fetched or modified, despite being present in the url.

Seeing it might be misleading for some users, maybe tokens for a component should be deleted (*or hidden) when the component gets published? @decidim/product @microstudi want to share any thoughts on this?

Edit: For now I'll just hide tokens when the component is not published.

I've found a bug. When there's more than one share token (I've test it with 3) from differents components, the visit counter don't work properly. It only increments with one token and not for all.
I show en example with the following video:
(...)

I've created first of all, a token for a survey that works fine. Then I've created a second token on another component (blog) that works fine. But for the third token (on the first component, the survey) I've check that there's no response changing the counter visit for it and also occured the same the first token. The only counter that increases is the blog token

I found the code correct. But I will still wait for the @decidim/product response on this small change in functionality.
Thanks @verarojman !

Seeing it might be misleading for some users, maybe tokens for a component should be deleted (*or hidden) when the component gets published? @decidim/product @microstudi want to share any thoughts on this?

For me, this "Share tokens" screen has a UX issue that's inherited from the rest of the admin panel: that we don't explain much about how this works and its behavior. I think that we should explain a bit about how it works and also that these tokens will get destroyed when the component is published.

@verarojman would you be so kind to add an explanatory text in the "Share tokens" panel explaining

how it works and also that these tokens will get destroyed when the component is published

@tramuntanal I've reviewed this PR and looks good to me. Thanks for the contribution @verarojman!