Bug/fix visState title when saving a new visualization#6296
Bug/fix visState title when saving a new visualization#6296repocho wants to merge 1 commit intoelastic:masterfrom repocho:bug/fix-visState-title
Conversation
|
Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then say 'jenkins, test it'. |
|
jenkins, test it |
|
@LeeDr the original issue was created by you. Perhaps you can review this PR also. |
|
LGTM I tested it and got the title saved; |
|
@panda01 if the code looks good to you I think it's good to merge |
|
I don't think this is an issue any longer. |
|
In your gif the title is not correct inside the visState object. This was the issue actually: I don't know the importance of this visState object when exporting it, but the issue is not solved in your gif. |
|
Whoops. Hmm I didn't see that honestly, but I can't see the point in it being in two places. Perhaps we should just remove it from the visState |
|
Hmm, so if you resubmit this pr, I'll get ti merged for you. I also was having trouble testing this, because in the merge from field, it says unknown repo. maybe you deleted the branch? |
|
Sorry @panda01 but as you said I've deleted the branch and I don't have the time to do this again. |
|
We can recreate it from the remote reference. |
|
Reissued in #7185 In case anyone's curious: |
Great ! Thanks @epixa |

title is not bound to visState object so we need to assign it to be able to save visState properly.
Closes #5901