-
Notifications
You must be signed in to change notification settings - Fork 18
feat(settings): 提供商与模型列表改为长按内容区排序 #16
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
Merged
+178
−171
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: jieapi/aicode
Length of output: 6276
🤖 get_repo_knowledge executed:
get_repo_knowledge jieapi/aicode /tmp/coderabbit-repo-knowledge/jieapi-aicode-ab458059Length of output: 343
🏁 Script executed:
Repository: jieapi/aicode
Length of output: 5369
🌐 Web query:
Jetpack Compose BoxScope.matchParentSize modifier measurement constraints Row padding fillMaxWidth official documentation💡 Result:
The matchParentSize modifier is a layout tool specific to the BoxScope, meaning it can only be used on direct children of a Box composable [1][2]. Its primary purpose is to allow a child element to size itself to match the dimensions of the parent Box without influencing the Box's own measured size [3][4]. Key characteristics include: Measurement Behavior: Unlike fillMaxSize, which causes the element to fill the available space and influences the parent Box's size calculation, matchParentSize is applied only after all other children (those not using matchParentSize) have been measured [3][2]. The Box determines its size based on those other children, and the matchParentSize child then adapts to these established dimensions [5][4]. Interaction with Constraints: Because matchParentSize does not affect the Box's measurement, it is frequently used to place background elements, such as spacers or images, that should span the same area as the content within the Box [1][2]. Limitations with Row and fillMaxWidth: - Scope: You cannot use matchParentSize inside a Row or Column because it is strictly defined within the BoxScope interface [1][5]. Attempting to use it outside of a Box will result in a compilation error [1]. - Composition: If you place a Row inside a Box and attempt to make that Row fill the Box's size using matchParentSize, the Row will match the dimensions determined by other non-matchParentSize children [3][4]. If the Row itself is intended to fill the width of the screen, you would typically use Modifier.fillMaxWidth on the Row itself [6]. Using fillMaxWidth on a child inside a Box causes that child to take up all available space, which in turn forces the Box to expand to that same size, contrasting with the behavior of matchParentSize [3][1]. If you need to apply sizing behaviors similar to matchParentSize within a Row, you must use Row-specific tools, such as the weight modifier, which is available in RowScope [2]. Similarly, LazyRow provides fillParentMaxWidth for items within its scope [7].
Citations:
Reserve the Test button area for metadata tags.
ModelMetadataTagsis a non-wrappingRowwith only start padding. Its available width does not excludeModelTestAreaWidth, so long tags can extend beneath the laterAlignment.CenterEndTest button. AddfillMaxWidth()and end padding equal toModelTestAreaWidth.🤖 Prompt for AI Agents
Source: MCP tools