Right now, the refreshPreferences() method is refreshing all preference data. This method is called on every preference partial view load. We should add some data to the partial preference views, in html, that allows us to specify which preference data we need. (Perhaps through the use of a lookup table and a data-required attribute on the first node?)
Alternatively, we could just go by the view id (so 'locations' would resolve to the data for 'locations', and 'level profiles' would correspond to the data for 'level-profiles').
Right now, the
refreshPreferences()method is refreshing all preference data. This method is called on every preference partial view load. We should add some data to the partial preference views, in html, that allows us to specify which preference data we need. (Perhaps through the use of a lookup table and adata-requiredattribute on the first node?)Alternatively, we could just go by the view id (so 'locations' would resolve to the data for 'locations', and 'level profiles' would correspond to the data for 'level-profiles').