I was using this with the https://github.com/Silvanite/novafieldcheckboxes field and the checkboxes get all scrunched due to w-1/2 getting applied to the inner field. I'm not sure if this is default field styling but it makes it so that larger fields are scrunched. Perhaps this should actually be fixed in the checkboxes field, but since this would be the parent element, I figured that perhaps this can be addressed here.

First of all: Thanks for the great package and the latest update with support for resolveUsing(...).

Any plans to also support displayUsing(...)? That does not seem to work... 🤔

Hello!

Using your package i've encountered a markup issue with longish json key names.
Screenshot attached.

I think we can display info lets say only one json attribute etc just to indicate data on index page?

An error gets returned if the value is null in the Resolve method:
json_decode() expects parameter 1 to be string, array given
In
$this->value = is_object($value) ? $value : json_decode($value);

Seems like the JSON fields are not validated. Would be really great to support this.

Is this something you are planning to implement in the future?

Hi,

fillUsing does not work. Does that still need to be added.

Thank you

I think field name should be JSON instead of Json . This caused me 20 minutes debugging. I should have identified when namespace was not being imported.

Any reason not to just merge this with the nova-fields package? It would make for one less loaded provider and enable the awesome customization available to those fields with styling classes.

Sometime only there is two fields it would be nice if we can see from index

Is there any way your package could add support for array casting?

I currently use a JSON column in my database which is cast to an array using the $casts attribute on my model.

When using nova-json the value sent to the field is already a valid JSON string, which throws an error when it is being parsed. This is pretty easy to fix by simply checking if the field value is an object or a string before parsing it.

The second issue is a bit harder to change, which is why I did not send a PR.
When submitting the form the value is stringified to a json string which is then parsed again by Laravel (because of the mutator) before updating the database.

Would it be possible to add an option to the field saying which cast is used, if any?

If the field is casted to an array then the Vue component shouldn't be dealing with JSON encoding/decoding.

I currently use a custom getter/setter which encode/decode the field accordingly but it seems a bit overkill...