feat: Export prevFieldMsg and nextFieldMsg#634
Open
colinodell wants to merge 1 commit intocharmbracelet:mainfrom
Open
feat: Export prevFieldMsg and nextFieldMsg#634colinodell wants to merge 1 commit intocharmbracelet:mainfrom
colinodell wants to merge 1 commit intocharmbracelet:mainfrom
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
1 participant
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.
When using fields outside of a
Group(as standalone components in a bubbletea application), it's impossible to tell that a user is done interacting with a field due to theprevFieldMsgandnextFieldMsgtypes being unexported; the parent model cannot check for (and thus handle) these messages.Would you be open to exporting those structs so they can be detected and acted on by non-huh parent components?