feat(admin): enhance TagInput with validation limits and template optimization#478
Merged
Merged
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.
feat(admin): enhance TagInput with validation limits and template optimization
📄 Summary
Enhance the
TagInputcomponent to provide a more robust and flexible tagging experience. This PR introduces strict validation enforcement (hard limits), prevents duplicate entries, and optimizes the internal template structure using Svelte 5 snippets. The component now offers better layout control and a more refined UI, aligning with the project's premium design standards.🧩 Affected Module
Component Updates
unstyledsupport to allow raw input rendering when used inside complex parent containers like TagInput. Exposed theonkeydownhandler for better event management.inlineflex property to support specialized layouts where the row should only occupy the width of its content.✅ Checklist
feat/add-taginput-component🔗 Related Issue
Closes #221