ReactJS: where to put validation logic in a form with "nested" composite components? -


i'm new reactjs , unsure best place put validation logic needed both nested child components in form, , overall "parent" form component itself. here over-simplified example illustrates question...

i have object represents pet owner:

{   name: 'jon arbuckle',   pets: [    { name: 'odie', type: 'dog' },    { name: 'garfield', type: 'cat' }   ] }

i'm using composite component called <petownerform> render form editing data. <petownerform> renders this:

<input type="text" value={name} /> <petlist value={petowner.pets} />

<petlist> composite component renders this:

<petlistitem value={this.props.value[i]} />  // render each pet... // buttons adding/deleting pets

<petlistitem> renders this:

<input type="text" value={this.props.value.name} /> <pettypepicker value={this.props.value.type} />

lastly, <pettypepicker> renders <select> <option>s pet types.

<pettypepicker> needs know how validate selected type can display inline error message (e.g., ensure value selected).

however, <petownerform> needs know how validate pet type because needs know how validate entire object (on load, each time form updated, , before submitting data server). if field invalid, "save" button should disabled.

so where, example, should "is valid pet type selected?" logic go? (bear in mind trivial example; in reality have many fields , nested composite components).

the options see far are:

a) replicate validation logic pet type (or whatever field) both in <petownerform> , <pettypepicker>. might matter of calling same, shared validation function in both places:

//petownerform.js: validate(petownerobj) {   util.ispettypevalid(petownerobj.pets[i]) // each pet   // validate other properties in petownerobj... }  //pettypepicker.js:   validate(pettype) {   util.ispettypevalid(pettype) }

b) use custom petowner, pet, , pettype models have own validators. way can ask model validate itself, regardless of is. maybe this:

{   name: { value: 'jon arbuckle', isvalid: ()=>{...} },   pets: [   {     name: { value: 'garfield', isvalid: ()=>{...} },     type: { value: 'cat', isvalid: ()=>{...} }    },    ...   ] }

c) modify petownerform.js go recurse pet owner object, validating each value, , setting 'errors' property child components can reference, resulting in object this:

{   name: { value: 'jon arbuckle asdfasdfasdf^^', errors: ['too many characters', 'contains invalid character']] },   pets: [     {       name: { value: '', errors: ['required value missing'] },       type: { value: 'tree', errors: ['invalid pet type'] }     },     ...   ] }

which option recommended react apps (or there option)?


Comments

Post a Comment

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

i have ec2 instance mongodb 3.2.0 installed. have user admin access. can connect user , perform operation remotely. 1 can connect database test remote if knows ip mongo 11.11.11.11. although not able make operations, want restrict access user credentials can connect server. first need create users , grant roles users, example: use admin db.createuser( { user: "myuseradmin", pwd: "abc123", roles: [ { role: "useradminanydatabase", db: "admin" } ] } ) then need start server --auth parameter mongod --auth more information here
Read more

r - Update two sets of radiobuttons reactively - shiny -

i have read ( how make choices in radiobuttons reactive in shiny? ) shows me how update radiobutton s in reactive way. however, when try , update 2 sets of buttons same data, 1 set renders. example: server: # create example data wafer <- rep(c(1:3), each=3) length <- c(1,1,2,1,1,1,3,5,1) width <- c(3,1,6,1,1,1,1,1,6) dd <- data.frame(wafer, length, width) shinyserver(function(input, output, session){ # create reactive dataframe store data values <- reactivevalues() values$df <- data.frame() # lengths , widths of wafer user input <- eventreactive(input$do, { subset(dd, wafer %in% input$wafer, select = length:width) }) # update reactive data frame lengths , widths have been selected user input observe({ if(!is.null(a())) { values$df <- rbind(isolate(values$df), a()) } }) output$wl <- renderdatatable({ a() }) # update radio buttons unique length , widths stored in values$df # ever "observe" put first in co...
Read more

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -

i'm working on app using core data , nsfetchedresultcontroller many reasons switch use realm. saw there "realm version" of nsfetchedresultcontroller on github wouldn't compatible current code using core data. the view controller displaying list of people same school, address book. list sublist of people studied in same city. so thinking make 1 unique request database retrieve list of people , filter locally list within 1 dictionary per school [string: anyobject] string section name within tableview , anyobject array of people. first solution, make nsfetchedresultcontroller each school predicate filtering location. delete actions etc.. handled delegates -> not compatible realm create dictionaries , update them each actions... -> works realm it's annoying code. any better solution? edit: i need clarify request: i'd write class inherit uitableviewcontroller. this class has list of people sorted in alphabetical order the tableview has ...
Read more