-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Integer Edit-mode Component #397
base: hotfix
Are you sure you want to change the base?
Add Integer Edit-mode Component #397
Conversation
Hi @mpuyosa91 we should add the PR or issue number to the commits |
01c4b24
to
2174e9b
Compare
2174e9b
to
f6235ad
Compare
Hey @mpuyosa91 ! I've given this a round of testing, and I've noticed some odd and inconsistent behaviour. First test: I then re-enter "12345a" Pressing save then seems to save the value "1234", (missing the 5) Second test: I then enter "5555555" Is this behaviour expected? Additionally, it seems to be clearing out the contents of the integer field when I enter in " , " or " . " or " ' " What are your thoughts? Thanks! |
When an integer field is modified, you can write non-numeric characters on it, this should not happen.
Description
core/app/core/src/lib/fields/int/templates/edit/*
: New Int component in edit view.core/app/core/src/lib/fields/base-fields.manifest.ts[110~111,120, 164, 214]
: Int component registration down'int.edit'
labelcore/app/core/src/lib/core.ts:364
Export created classesMotivation and Context
In an integer-type field, you should not be able to write non-decimal characters.
How To Test This
INT FIELD
field, modify it with any value, and try to add a non-decimal character; save.Test Environment
public/legacy/custom/Extension/modules/Contacts/Ext/Vardefs/int_field.php
public/legacy/custom/Extension/modules/Contacts/Ext/Language/en_us.int_field.php
public/legacy/custom/modules/Contacts/metadata/detailviewdefs.php
public/legacy/custom/modules/Contacts/metadata/editviewdefs.php
Types of changes
Final checklist