Sorry but I am unable to comprehend 'saved state'.
Does this mean 'saving it for a session' (in sessionStorage may be)
or
introducing required number of config options (and these options value will be set every time the 'angular' links are changed to 'direct' or vice versa through designer) ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is an interesting question because most of the rest of the information about Designer display is stored in the phpMyAdmin Configuration Storage, for instance $cfg['Servers'][$i]['table_coords'] and $cfg['Servers'][$i]['pdf_pages'].
I wonder if we could implement some way of storing this in the phpMyAdmin Configuration Storage.
"Saved state" preferably means remembering it forever across sessions, but sessionStorage might be acceptable as well. I think we can ask on -devel for some assistance with brainstorming about this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Sorry but I am unable to comprehend 'saved state'.
Does this mean 'saving it for a session' (in sessionStorage may be)
or
introducing required number of config options (and these options value will be set every time the 'angular' links are changed to 'direct' or vice versa through designer) ?
This is an interesting question because most of the rest of the information about Designer display is stored in the phpMyAdmin Configuration Storage, for instance $cfg['Servers'][$i]['table_coords'] and $cfg['Servers'][$i]['pdf_pages'].
I wonder if we could implement some way of storing this in the phpMyAdmin Configuration Storage.
"Saved state" preferably means remembering it forever across sessions, but sessionStorage might be acceptable as well. I think we can ask on -devel for some assistance with brainstorming about this.
Implemented with https://github.com/phpmyadmin/phpmyadmin/pull/1737