Skip to content
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

Fix dynamic select get value an object #71

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

ahmadrio
Copy link

No description provided.

@@ -33,13 +33,18 @@
}
},

created() {
Nova.$on('nova-dependency-container-' + this.field.attribute, this.dependencyChange)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this accomplish?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it used for another components to call this component field

@wize-wiz
Copy link
Contributor

wize-wiz commented Oct 4, 2019

@opanegro could you supply an example code on how to test this? Or can you verify the problem still exists in the latest version?

@@ -73,7 +77,7 @@
return;
}

if(dependency.hasOwnProperty('value') && this.dependencyValues[dependency.field] !== dependency.value) {
if(dependency.hasOwnProperty('value') && this.dependencyValues[dependency.field] != dependency.value) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I would say this change would be good, since first you as a dev should know what the value is that you are checking against, but also there are some odd type behaviors in JS that I don't think we want to mess with.
Is there a specific reason to convert this from !== to a !=?

$this->extractChildFields($field->meta['fields']);
} else {
$availableFields[] = $field;
if (!is_null($this->action()->fields())) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How would the action fields ever be null? That's not the method signature of the method that returns fields and is more likely a problem with not following that method signature over a bug. That being said, do you have an example of this being an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants