Skip to content

Releases: dewsign/nova-repeater-blocks

Return resolvable attribute

05 May 12:39
35275bb

Choose a tag to compare

This patch release fixes the attribute resolution found in the resolveAttribute method.

Polymorphic relation redundancy with graceful failure

14 Apr 16:00
b9ec269

Choose a tag to compare

Release adds graceful failure to Polymorphic relations

What's Changed

  • Update to prevent non-render when stale, broken Polymorphic relation by @hrefdev in #32

New Contributors

Full Changelog: v1.8.9...v1.9.0

Improvements to search results

22 Jan 13:49

Choose a tag to compare

Work around issue with naming

14 Nov 09:55

Choose a tag to compare

Laravel 6 compatibility

21 Oct 12:54

Choose a tag to compare

Repeater json directive

16 Sep 10:18

Choose a tag to compare

Added a helper for json output (Handy for Javascript front ends). Same as before, just pass the model in to generate json output.

@repeaterjson($model)

Added a fallback for `viewable` on RepeatableBelongsTo field.

17 Jul 10:09

Choose a tag to compare

Added a fallback for $this->viewable on the RepeatableBelongsTo field. We missed this during the upgrade to Nova 2.0.

Delete image when repeater block is deleted

17 May 07:49

Choose a tag to compare

Previously, when deleting a repeater image block, the source file was not deleted. This addresses that issue and deletes the source file through the ImageProcessor. This makes is super easy to customise the delete functionality for remote drivers such as Cloudinary.

Important: If you created your own ImageProcessors and these do not extend the packages base image processor you will need to update them to ensure that they either extend Dewsign\NovaRepeaterBlocks\Processors\ImageProcessor or include a static delete method as shown in the Readme.

v1.5.0

27 Mar 15:23

Choose a tag to compare

Nova 2.0 introduced a reverse meta field which throws an error when using BelongsTo fields in Repeaters. You'd typically never have a reverse relationship on nested repeaters so we avoid this situation by using the included RepeatableBelongsTo field instead.