- First commit to issue fork.
- 🇦🇺Australia acbramley
So we can do something like this (in MR) to use the views URL directly so changing the path won't break the block, but this block has several other issues which I'm not even sure if it's worth fixing (does anyone use this block??)
1. Has a block_count config which does nothing. This will need an update path to remove the config, etc.
2. Config dependencies - the block should depend on the view
3. Access controls - The block shouldn't render if the view or display doesn't exist - what happens if someone renames the display from feed_1? Should we just hide the block in those cases?
4. Cacheability - the block render cache needs to depend on the views config. - 🇦🇺Australia acbramley
Let's deprecate the whole thing 📌 Deprecate SyndicateBlock Active
