Is it possible that this is a bug, since they are quite often used as field names.
Mongoid::Errors::InvalidField (
translation missing: sl.mongoid.errors.messages.message_title:
translation missing: sl.mongoid.errors.messages.invalid_field.message
translation missing: sl.mongoid.errors.messages.summary_title:
translation missing: sl.mongoid.errors.messages.invalid_field.summary
translation missing: sl.mongoid.errors.messages.resolution_title:
translation missing: sl.mongoid.errors.messages.invalid_field.resolution):
vendor/ruby/2.3.0/gems/mongoid-6.2.0/lib/mongoid/fields/validators/macro.rb:75:in `block in validate_name'
vendor/ruby/2.3.0/gems/mongoid-6.2.0/lib/mongoid/fields/validators/macro.rb:73:in `each'
vendor/ruby/2.3.0/gems/mongoid-6.2.0/lib/mongoid/fields/validators/macro.rb:73:in `validate_name'
vendor/ruby/2.3.0/gems/mongoid-6.2.0/lib/mongoid/fields/validators/macro.rb:35:in `validate'
vendor/ruby/2.3.0/gems/mongoid-6.2.0/lib/mongoid/fields.rb:268:in `field'
Works fine in 6.1.1.
by
TheR
- is duplicated by
-
MONGOID-4466 options and client are prohibited field names after upgrading to 6.1
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
-
- Closed
-