Skip to content
This repository has been archived by the owner on Jun 23, 2020. It is now read-only.

rethink the naming of enabled/disabled/readonly/label fields #37

Open
szimano opened this issue Feb 20, 2015 · 0 comments
Open

rethink the naming of enabled/disabled/readonly/label fields #37

szimano opened this issue Feb 20, 2015 · 0 comments
Labels
API backend frontend

Comments

@szimano
Copy link
Member

szimano commented Feb 20, 2015

Having ease of use in mind.

  1. Try to be inline with the current nomenclature used in web frameworks
  2. Provide with positive/negative options (like .enabledIf( ... ); .disabledIf( ... ) )
@szimano szimano changed the title rething the naming of enabled/disabled/readonly/label fields rethink the naming of enabled/disabled/readonly/label fields Mar 3, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
API backend frontend
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@szimano