Reviewed & tested by the community
Project:
IMP
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
26 Mar 2014 at 13:15 UTC
Updated:
27 Mar 2014 at 13:26 UTC
Jump to comment: Most recent, Most recent file
Number and email modules are now part of field module as for #2218199: Move email and number field types to \Drupal\Core\Field, remove modules
These tests are broken probably because of this:
Fixing it right now
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 2226393-fixing_tests-7.patch | 11.3 KB | pcambra |
| #4 | 2226393-fixing_tests-4.patch | 10.65 KB | pcambra |
| #1 | 2226393-fixing_tests.patch | 6.67 KB | pcambra |
Comments
Comment #1
pcambraI've just pushed this patch but we need to investigate further some other tests that are failing still.
Comment #2
pcambraComment #3
benjy commentedThese are the incoming values? Shouldn't we be changing the mapped value?
Comment #4
pcambraThis is another patch fixing the tests, I'll take care of #3 in the next "batch".
Comment #5
benjy commentedWhy isn't the number type mapped in yaml if the value comes from the source?
I thought that we just changed this because core now has integer rather than number_integer? #2218199: Move email and number field types to \Drupal\Core\Field, remove modules
Comment #6
pcambraThanks a lot for the review @benjy I might have done some mistakes because we've spent too much time figuring this already :)
About #1, I was getting errors on the module discovery, as number module is not there anymore but is part of field/core now, it wasn't detecting what the thing coming was so I'm doing a fallback to the type, which seemed to be fine. Not sure what other option would be.
About #2, field type is now "integer" but formatter is still "number_integer"
Comment #7
pcambraOk, reviewed it and #3 and #5.1 were related, this should be better.
Comment #8
benjy commentedAwesome!