Current translations have many grammar mistakes and overall incomprehensible sentences. I updated a lot of them. Any constructive feedback is welcome.

I think this might be because the translatable attribute in \JanVince\SmallRecords\Models\Attribute model has pivot[value_string] for the translatable value but the translation plugin doesn't pick that up and save the translated values. Probably because it's a pivot model, but I'm not sure on that.

@mjauvin is it possible to make custom attributes translatable too? I am using them but they don't show up on translations page.

Title feels weird, I didn't know how to explain it better and as short as possible.

Demo: https://codepen.io/hkanaktas/pen/JjYzqyq

Expected behavior

"fish are weird" should get removed when I click reset obj button.

Current behavior

"fish are weird" string is forgotten on the page. And more is added as the set fish button is clicked after resetting the object.

Extra info

My real use case here is: I have a validationErrors object. I set Laravel's error data (which is in Object<Array<String>> format) from 422 responses. When user resubmits the form, I simply reset them with validationErrors = {} before sending the request but the errors stay on page. But interesting enough that I don't get that repeating behavior in the demo pen.

Is this somehow my error? Maybe wrong key? Should I loop over the errors in another way?

Ah, damn. I knew something was wrong with my code. Thanks Simone!

Title feels weird, I didn't know how to explain it better and as short as possible.

Demo: https://codepen.io/hkanaktas/pen/JjYzqyq

Expected behavior

"fish are weird" should get removed when I click reset obj button.

Current behavior

"fish are weird" string is forgotten on the page. And more is added as the set fish button is clicked after resetting the object.

Extra info

My real use case here is: I have a validationErrors object. I set Laravel's error data (which is in Object<Array<String>> format) from 422 responses. When user resubmits the form, I simply reset them with validationErrors = {} before sending the request but the errors stay on page. But interesting enough that I don't get that repeating behavior in the demo pen.

Is this somehow my error? Maybe wrong key? Should I loop over the errors in another way?

Ah, makes sense. Thanks for the explanation Simone. Issue can be closed if it's a wontfix.

Re-setting the same value in $nextTick was the first thing I tried. It doesn't work. Binding :selected seems to work.

There are some issues with which option is selected when select's options are generated with x-for. See pen for demo.

Pen: https://codepen.io/hkanaktas/pen/vYNVJYL?editors=1000

Expected behavior

Both selects should display "cucumbers" after the page loads and Alpine initiates component.

Observed behavior

The select with a static option (after x-for'd options) shows the static option as selected. Other one shows the first option as selected.

Notes

See how selects get correct option selected when you cause any changes in component data. Maybe this issue can be solved by triggering a forced update after selects with x-for'd options are rendered?

@Ragash yeah the whole auto-discovery thing is rather flimsy. See the last commit on my fork for the simplest way to change it.