Skip to content

Fix fieldtype Vue component issues#156

Merged
riasvdv merged 2 commits intospatie:mainfrom
ncla:fieldtype-vue-fix
Aug 27, 2022
Merged

Fix fieldtype Vue component issues#156
riasvdv merged 2 commits intospatie:mainfrom
ncla:fieldtype-vue-fix

Conversation

@ncla
Copy link
Copy Markdown
Collaborator

@ncla ncla commented Aug 16, 2022

From what I found, setting this.value = value; seems redundant and the value updates, saves correctly with just this.update(value);. Removing this line fixes the warning #155

Adding :trackDirtyState="false" fixes the dirty state part of the #120 issue. The issue was if you were to save an entry with "Go to listing" save option, it would unnecessarily, annoyingly trigger the "Reload site?" prompt. The dirty state tracking still works as this ResponsiveFieldtype component is a child of another PublishContainer component which already has dirty state tracking. I assume wherever this ResponsiveFieldtype might appear, a parent component PublishContainer has dirty state tracking anyway.

@ncla ncla changed the title Fix fieldtype Vue component issues #155, #120 Fix fieldtype Vue component issues Aug 16, 2022
@riasvdv riasvdv merged commit 9543ba5 into spatie:main Aug 27, 2022
@riasvdv
Copy link
Copy Markdown
Contributor

riasvdv commented Aug 27, 2022

Thanks!

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.

2 participants