Add Long Text to custom field type selector - #220
Open
rsaether76 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Paperless-ngx
longtextas a selectable custom field type in the Paperless-AI Next settings UI.Paperless-AI Next already preserves configured
longtextcustom fields throughCUSTOM_FIELDS, and the shared custom field validator only applies the 128-character length guard tostringfields. This change lets users select long text fields from the settings page instead of manually editing Docker environment JSON.Changes
Long Text/longtextto the custom field type dropdown inviews/settings.ejs.longtextoption.Testing