You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here you can see that directive params (entity and id) are always overriden with state params (entry and id from object which is returned from $state.params call).
In practice it causes wrong behaviour whenever we try to place Delete button in other entity's view. For example I have Post which may have many Images and use referenced_list field type to view list of related Images in Post's edit view. If i place <ma-delete-button entry="::entry" entity="::entity()" size="xs"></ma-delete-button> directive to the refernced_list table (as template field type), delete button will direct user to the Post deletion view, not Image deletion view. This is a bug, and I've made a fix for it: vasiakorobkin/ng-admin@2534ba3
The text was updated successfully, but these errors were encountered:
Here you can see that directive params (
entity
andid
) are always overriden with state params (entry
andid
from object which is returned from$state.params
call).In practice it causes wrong behaviour whenever we try to place
Delete
button in other entity's view. For example I havePost
which may have manyImages
and usereferenced_list
field type to view list of relatedImages
inPost
's edit view. If i place<ma-delete-button entry="::entry" entity="::entity()" size="xs"></ma-delete-button>
directive to therefernced_list
table (astemplate
field type), delete button will direct user to thePost
deletion view, notImage
deletion view. This is a bug, and I've made a fix for it: vasiakorobkin/ng-admin@2534ba3The text was updated successfully, but these errors were encountered: