1
[Feature Request] Trim string in monetary custom field
Source: paperless-ngx/paperless-ngx#14544 · opened by @tofuwabohu
Description
Copying a monetary value from a OCR-ed scanned document sometimes adds leading or trailing spaces. These are easy to miss but prevent the validity check from the custom field. I'd suggest they get trimmed automatically.
Other
I did a quick research and there don't seem to be any currencies delimited by space. There might be spaces between powers of thousand (e.g. 7 654 321) which might get trimmed when adding them via keyboard, but since we store as float, these can be ignored anyways.
Copying a monetary value from a OCR-ed scanned document sometimes adds leading or trailing spaces. These are easy to miss but prevent the validity check from the custom field. I'd suggest they get trimmed automatically.
Other
I did a quick research and there don't seem to be any currencies delimited by space. There might be spaces between powers of thousand (e.g. 7 654 321) which might get trimmed when adding them via keyboard, but since we store as float, these can be ignored anyways.
No pledges yet. Be the first to back this.
Comments
Similar requests
Custom fields per document type with matching algorithms
1 vote · 0 comments
[Feature Request] Using custom fields in workflow title templates
36 votes · 0 comments
[Feature Request] Nested Custom Fields and Custom Fields of Type Class and List
12 votes · 0 comments
[Feature Request] New Custom Field Type: Choose with Complex Type
1 vote · 0 comments
[Feature Request] Email metadata to Custom Fields
14 votes · 0 comments
No comments yet.