ruby on rails - YAML File has a syntax error, but it looks like it has the same format as another one that is working? -


i have 2 yaml files similar formats, 1 running , other not running when run integration tests on rails app.

here first yaml file doesn't work:

prince_edward_island:   name: 'prince edward island'   country: 'canada'

nova_scotia: name: 'nova scotia' country: 'canada'

newfoundland:   name: 'newfoundland'   country: 'canada'  new_brunswick:   name: 'new brunswick'   country: 'canada'  quebec:   name: 'quebec'   country: 'canada'  manitoba:   name: 'manitoba'   country: 'canada'  alberta:   name: 'alberta'   country: 'canada'  ontario:   name: 'ontario'   country: 'canada'  british_columbia: 'canada'   name: 'british columbia'   country: 'canada'  saskatchewan: 'canada'   name: 'saskatchewan'   country: 'canada'

here second yaml file work:

student_advisor_message:   body: 'this message'   subject: 'subject!'   user: student_advisor  manager_message:   body: 'this message'   subject: 'subject!'   user: manager  read_manager_message:   body: 'this message'   subject: 'subject!'   user: manager  agent_manager_message:   body: 'this message'   subject: 'subject!'   user: agent_manager  message_for_jack:   body: 'this message'   subject: 'subject!'   user: manager  message_for_jack_sent:   body: 'this sent message'   subject: 'sent subject!'   user: manager  message_for_jack_trash:   body: 'this trashed message'   subject: 'trash subject!'   user: manager

the error is: 

error:  while parsing block mapping   in "<unicode string>", line 1, column 1:     prince_edward_island:     ^ expected <block end>, found '<block mapping start>'   in "<unicode string>", line 34, column 3:       name: 'british columbia'

can explain difference missing between two? both use spaces, not tabs.

there several errors:

for both use tabs, not spaces.

tabs not allowed indentation characters in yaml.

country: 'canada'    nova_scotia:

here, give both scalar ('canada') , mapping (starting nova_scotia:) value key country. there may 1 value key. either have remove scalar 'canada' or move mapping contains elsewhere.

british_columbia: 'canada'   name: 'british columbia'   country: 'canada'  saskatchewan: 'canada'   name: 'saskatchewan'   country: 'canada'

here, make same error again twice.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more