-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Array/callback support (Feature request) #20
Comments
Having a Iterable field i was able to solve this by updateting the NovaDependencyContainer.php to show: ` public function resolveForDisplay($resource, $attribute = null)
` |
What is the corresponding change to FormField.vue to make this work on the front end also? |
I was not able to fix the VUE part :)
…On Mon, Dec 10, 2018 at 7:27 PM dtannen ***@***.***> wrote:
What is the corresponding change to FormField.vue to make this work on the
front end also?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGNQNQUQYO2iFM1-5cunf3dX0TGTF2kbks5u3pmJgaJpZM4XIHvT>
.
--
Valentin Ceaprazaru
CodingHeads.com
<http://codingheads.com/?utm_source=emailClient&utm_medium=email>
|
I updated the VUE part and submitted a pull request |
Maybe PullRequest #56 can help as it accepts values in an array. |
I hope that this feature request is still active. I too could really use a different mechanism for value comparison. |
@aedart no it's not active, I'm currently working on different solution. Callback is not possible, this will just not work. |
@wize-wiz, ok. Thanks for your quick reply :) |
Maybe a nice feature is making the ability to pass in an array with values on which the value of the input filed gets checked. If the value is in the array then the container should show. Whereas now it only accepts one value per field.
It could look like so
Or you could even make it a callback.
The text was updated successfully, but these errors were encountered: