Config Editor: Visibility of Inherited checkbox

Description

The "Inherited" checkbox should be only shown if there is a higher configuration level, and if there is a value provided from that can be inherited from.

And - this is cosmetic - if it is possible it would be nice if checking and unchecking the "inherited" checkbox without saving in between, the value previously entered will be displayed again. If an editor uses this checkbox by accident he can revert easily without having to reload the whole page.

Activity

Show:
Igor Sechyn
October 14, 2014, 8:45 AM

done

Stefan Seifert
October 14, 2014, 8:13 AM

yes, please

Igor Sechyn
October 14, 2014, 7:37 AM

Should I include nodejs plugin back into the build chain? Otherwise the package does not contain the templates and the editor is not usable.

Igor Sechyn
October 14, 2014, 7:02 AM

I am generating a test template module with some mock markup to test directives.

that was a bug. I was generating this file only in the "test" grunt task, but forgot to include it into the "build" profile". I have removed the test-Template.js and included it into gitignore again and fixed the grunt "build" profile.

Igor Sechyn
October 13, 2014, 11:02 PM

hmmm, this is weird. I am generating a test template module with some mock markup to test directives. I added it to svn ignore since it is generated on each karma run, but travis seems to have problems with this. I have added it back to repository. This should fix it.

Fixed

Assignee

Unassigned

Reporter

Stefan Seifert

Labels

None

Components

Fix versions

Priority

Trivial