Attach library to AddToAny render arrays, and add option to only load AddToAny assets upon module use

Rerolled #22 aganist 1.18.

Changed the status to "Needs review"

Just read the points made by @micropat in #20. Not sure if this work has been done already on the dev branch. Are them still applicable?

Moving back to Needs work.

@unstatu Nothing in the dev branch yet! A patch per #20 is very welcome for 8.x-1.x & 2.0.x and would be a feature highlight in the next release.

Rerolled #22 againts 2.0

@ddiestra

It looks like the mentioned library in the patch "addtoany/addtoany" doesnt exist in 2.0

Rerolled #22 againts 2.0

Patch #28 works for me

Checking if committed ✨ Cache external addtoany JS library and update the local cache with cron Needs review solved the issue?

Some additional work needed is outlined in #20. Patches welcome!

Added a patch to load the AddtoAny library only on pages where the social share buttons are used.

Patch requirements on the dev branch so this feature can make a stable release:

1. Add a new limit_loading boolean config option (default false per #17).
2. Add the limit_loading checkbox option in AddToAny config > Additional Options:
   

   [ ] Only load AddToAny assets on pages that actively use this module.
       When enabled, dynamic AddToAny features and custom code may not work on all pages.

3. In addtoany_page_attachments(), conditionally attach the addtoany library based on the limit_loading option.
4. Attach the addtoany library to all AddToAny render arrays.

Patch #33 works for me (2.0.4)

Why not work on the MR created on comment #7 https://www.drupal.org/project/addtoany/issues/3056377#comment-13964345 ✨ Attach library to AddToAny render arrays, and add option to only load AddToAny assets upon module use Needs work instead of reroll constantly over the same changes?

After reading comment #34 we understand that the solution is to attach the library add to any to the addtoany-standard template, and also add a configuration to load always the addtoany library to avoid errors on Ajax petitions on the preprocess page.

The patches for this stopped working for us after a recent module update. Inspecting the most recent patch version (under issue fork - plain diff), I can see that most of the changes are now in the module.

This is the same patch in comment #33, to make it work with the last update for the module.