when trying to save something like 111111111111111 its being converted to 1.1111111111111E+14 in range_field_presave, use number format instead
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | range-change_roud_to_numbeer_format-2693493-1.patch | 1.31 KB | josebc |
when trying to save something like 111111111111111 its being converted to 1.1111111111111E+14 in range_field_presave, use number format instead
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | range-change_roud_to_numbeer_format-2693493-1.patch | 1.31 KB | josebc |
Comments
Comment #2
josebc commentedpatch file
Comment #3
anas_maw commentedThis patch for 7.x-1.1 version
Comment #8
anas_maw commentedComment #10
taran2lPatch looks good to me.
Comment #11
taran2lComment #12
josebc commentedHello
I think you didn't notice but you applied the wrong patch
Comment #13
taran2lHi josebc,
Patches are identical actually in terms of functionality.
I've applied your patch, but missed the correct radio button when I was generating commit message. Sadly, Drupal infrastructure doesn't allow for amending git history. Sorry for that.
Comment #14
taran2lI think I can revert commit and create a new one with your authorship. Does this work for you?
Comment #15
taran2lBtw, the same issue exists in core Number field for both D7 and D8.
Comment #17
taran2lAh, patch breaks existing functionality! Reverted.
Comment #18
taran2lComment #19
josebc commentedIts ok, its just that the other patch was the same as the first one expect that the second was rerolled to apply against an old version which is wrong
No worries for the attribution what matters is that the issue is resolved
Comment #20
taran2lthis actually should be fixed by an updated validation in the version 1.8