v0.6.2

What's Changed

• docs: updated docs with update checker config by @crezra in #74
• docs: added upload validation documentation by @crezra in #75
• fix(flexible): fix flexible support by @mikaelpopowicz in #77

Full Changelog: v0.6.1...v0.6.2

0.6.1

What's Changed

• fix: added missing update checker banner by @crezra in #73

Full Changelog: v0.6.0...v0.6.1

0.6.0

What's Changed

• Add workflow to automatically update assets via nova-kit/nova-packages-tool by @crynobone in #64
• Bump supported version with Script ordering fixes. by @crynobone in #65
• test: add guzzle to fix browser test. by @mikaelpopowicz in #66
• Minor fixed and UI improvements by @mikaelpopowicz in #67
• refactor: refactor index field by @mikaelpopowicz in #68
• Support filesystem as string by @milewski in #69
• feat(upload): add upload rules and upload custom validation by @mikaelpopowicz in #71
• feat(flexible): add flexible content support by @mikaelpopowicz in #72
• feat: add update checker banner message by @crezra

New Contributors

• @crynobone made their first contribution in #64

Full Changelog: v0.5.0...v0.6.0

0.5.0

🚨 BREAKING CHANGE

Warning

Existing assets saved with the field will not work anymore once you update the tool, please migrate your existing data when updating the package.

This PR introduces a major breaking changing related to how the data is saved in the database, initially we tried to follow Laravel Nova's built-in fields as much as possible by having a two column set up to save the asset's path and then the asset's disk if needed. However, this approach isn't as reliable as we hoped for it to be. There was indeed a particular use case that wasn't in our scope when building the field, when saving multiple assets from different disks, only the one disk was to be saved in the disk column and that makes the tool behaves in unintended ways.

We have moved forward with a JSON schema to save the field's data.

Starting from the next 0.5 release, the data will change from :

image	image_disk
<image-path-value>	<disk-name>

TO

image
{"path": "<image-path-value>", "disk": "<disk-name>" }

So in other words, each asset that will saved with its corresponding disk.

We regret to introduce such a change so early, but it is a change that needs to be done unfortunately.

To migrate your existing data, you may defined a command or action to transform your data to the required schema.

What's Changed

• fix(docs): updated screenshots in docs by @crezra in #59
• Add crop image feature by @mikaelpopowicz in #60
• [0.5.x] Improved multi disk support, added image cropping by @mikaelpopowicz in #63

Full Changelog: v0.4.0...v0.5.0

0.4.0

What's Changed

• Add field and tool permissions. by @mikaelpopowicz in #49
• fix(file-card): fixed missing file label spacing and alignment by @crezra in #56
• fix(file-card): fixed file card submitting the form by @crezra in #57
• fix(disks): fixed path not resetting when changing disks by @crezra in #58

Full Changelog: v0.3.2...v0.4.0

0.3.2

What's Changed

• sync by @crezra in #47
• ♿️ fixed focus styles for better accessibility by @crezra in #48

Full Changelog: v0.3.1...v0.3.2

0.3.1

What's Changed

• Improve selection and accessibility by @mikaelpopowicz in #46

Full Changelog: v0.3.0...v0.3.1

0.3.0

What's Changed

• v0.3.0 by @crezra in #45

Full Changelog: v0.2.7...v0.3.0

0.2.7

What's Changed

• 💄 fixed some minor UI issues by @crezra in #43

Full Changelog: v0.2.6...v0.2.7

0.2.6

What's Changed

• 🔧 added algolia docsearch by @crezra in #35
• 📈 added tinyanalytics to docs by @crezra in #36
• 📈 fixed tinyanalytics setup by @crezra in #37
• 📈 replace tinyanalytics with splitbee by @crezra in #38

Full Changelog: v0.2.5...v0.2.6