<optionname="instructions"value="Your task is to find potential bugs in the given code snippet. Carefully examine the code for potential bugs, logical errors, or common programming mistakes. Consider issues such as: - Syntax errors - Off-by-one errors - Null pointer exceptions - Memory leaks - Infinite loops - Incorrect logic - Unhandled exceptions Provide a concise list of potential bugs you've identified. If you don't find any bugs, state that the code appears to be bug-free based on your analysis. Here's the code to analyze: {SELECTION}"/>
<optionname="name"value="Find Bugs"/>
</ChatActionPromptDetailsState>
<ChatActionPromptDetailsState>
<optionname="code"value="WRITE_TESTS"/>
<optionname="id"value="2"/>
<optionname="instructions"value="Your task is to create concise, effective tests for the given code. Generate unit tests for the provided code. Focus on: 1. Testing main functionalities 2. Edge cases 3. Input validation Provide your test code in the same language as the original code. Use common testing frameworks and assertions appropriate for the language. Here's the code to write tests for: {SELECTION}"/>
<optionname="name"value="Write Tests"/>
</ChatActionPromptDetailsState>
<ChatActionPromptDetailsState>
<optionname="code"value="EXPLAIN"/>
<optionname="id"value="3"/>
<optionname="instructions"value="Your task is to provide a clear, concise explanation of what this code does. Focus on the main functionality and purpose of the code, avoiding unnecessary details. Explain any complex logic or algorithms if present. Provide your explanation in a few sentences, using simple language that a junior programmer could understand. If there are any notable best practices or potential improvements, briefly mention them at the end. Here's the code to analyze: {SELECTION}"/>
<optionname="name"value="Explain"/>
</ChatActionPromptDetailsState>
<ChatActionPromptDetailsState>
<optionname="code"value="REFACTOR"/>
<optionname="id"value="4"/>
<optionname="instructions"value="Your task is to improve the code's readability, efficiency, and maintainability without changing its functionality. Follow these steps: 1. Analyze the following selected code: 2. Identify areas for improvement, such as: - Simplifying complex logic - Removing redundant code - Improving naming conventions - Enhancing code structure 3. Refactor the code, keeping these guidelines in mind: - Maintain the original functionality - Follow best practices for the programming language used - Prioritize readability and maintainability Be concise in your explanation, focusing on the most important improvements made. Here's the code to refactor: {SELECTION}"/>
<optionname="name"value="Refactor"/>
</ChatActionPromptDetailsState>
<ChatActionPromptDetailsState>
<optionname="code"value="OPTIMIZE"/>
<optionname="id"value="5"/>
<optionname="instructions"value="Your task is to improve the code's efficiency, readability, and adherence to best practices without changing its core functionality. Analyze the code and suggest optimizations that could improve its performance, readability, or maintainability. Focus on: 1. Reducing time complexity 2. Improving space efficiency 3. Enhancing code readability 4. Applying relevant design patterns or coding best practices Provide your optimized version of the code, along with brief comments explaining the key changes and their benefits. Keep your response concise and focused on the most impactful optimizations. Here's the code to optimize: {SELECTION}"/>
<optionname="name"value="Optimize"/>
</ChatActionPromptDetailsState>
</list>
</option>
</ChatActionsState>
</option>
<optionname="coreActions">
<CoreActionsState>
<optionname="autoApply">
<CoreActionPromptDetailsState>
<optionname="code"value="AUTO_APPLY"/>
<optionname="instructions"value="You are an AI assistant specialized in integrating code changes into an existing file. Your task is to analyze the provided code snippet and determine how to properly integrate it into the target file. First, here is the project information: <project_path> {{project_path}} </project_path> Here are the code changes that need to be merged: <changes_to_merge> {{changes_to_merge}} </changes_to_merge> The file where you should merge the changes: <destination_file> {{destination_file}} </destination_file> When making code changes, follow these steps: 1. Analyze the integration requirements: Wrap your analysis in <integration_analysis> tags, addressing the following points: - Summarize the purpose of the new code - Identify where in the target file it should be placed - List any new imports or dependencies that need to be added - Note any existing code that needs to be modified or replaced - Consider potential conflicts or side effects of the integration - Does it replace existing functionality or add new functionality? 2. Provide a brief reasoning explanation (2-3 sentences) about your integration strategy 3. Generate precise SEARCH/REPLACE blocks for each change needed Format your output according to these rules: - Start with "Integration Strategy: [brief explanation of your approach]" - For each change, write a description: "Operation N: [what the change does]" - Each operation gets its own markdown code block - Start with the opening fence and code language, followed by the file path e.g., ```python:/path/to/file - Provide the full file path on the same line after a colon - Use <<<<<<< SEARCH to start the search block - Include the exact lines to search for in the EXISTING target file content - Use ======= as a dividing line - Provide the lines to replace into the target file - Use >>>>>>> REPLACE to end the replace block - Close with the closing fence: ``` Important guidelines: - The SEARCH section must contain code that ALREADY EXISTS in the target file - The REPLACE section contains the MODIFIED version with the new code integrated - Never search for code from the "changes_to_merge" section - that's what you're adding! - Each search pattern must be COMPLETELY UNIQUE within the file - Include enough context to make each search pattern unique - NEVER use generic patterns like single characters or common whitespace - Search patterns must be at least 3 characters long - If a pattern appears more than 3 times, include more surrounding context Here's an example of how your output should be structured: Integration Strategy: [Brief explanation of overall approach] Operation 1: [Description of first change] Reasoning: [Brief explanation for this specific change] ```[language]:/path/to/file <<<<<<< SEARCH [existing code to search for] ======= [modified code with changes integrated] >>>>>>> REPLACE ``` Operation 2: [Description of second change] Reasoning: [Brief explanation for this specific change] ```[language]:/path/to/file <<<<<<< SEARCH [existing code to search for] ======= [modified code with changes integrated] >>>>>>> REPLACE ``` GOOD practices: - Each operation in its own code block - Clear reasoning before operations - Finding appropriate insertion points in the target file - Preserving existing code structure and style - Including enough context to ensure unique matches BAD practices (AVOID): - Searching for the new code in the target file - Creating search patterns from the "Code to Apply" section - Using generic patterns that could match multiple locations - Generating the entire file content - Missing the reasoning step Remember to provide clear reasoning before each operation and ensure that your search patterns are unique and contextually rich."/>
<optionname="name"value="Auto Apply"/>
</CoreActionPromptDetailsState>
</option>
<optionname="fixCompileErrors">
<CoreActionPromptDetailsState>
<optionname="code"value="FIX_COMPILE_ERRORS"/>
<optionname="instructions"value="I will provide you with a snippet of code that is causing a compilation error. Your task is to identify the potential causes of the compilation error(s) and propose code solutions to fix them. Please approach this step by step, explaining your reasoning as you go."/>
<optionname="instructions"value="Branch: {BRANCH_NAME} Date: {DATE_ISO_8601} Write a short and descriptive git commit message for the following git diff. Use imperative mood, present tense, active voice and verbs. Your entire response will be passed directly into git commit."/>
<optionname="instructions"value="Provide five alternative names for a given function or method body. Your response should be a list of names, separated by commas, without any extra information. "/>
<optionname="name"value="Generate Name Lookups"/>
</CoreActionPromptDetailsState>
</option>
<optionname="inlineEdit">
<CoreActionPromptDetailsState>
<optionname="code"value="INLINE_EDIT"/>
<optionname="instructions"value="You are a code modification assistant. Generate SEARCH/REPLACE blocks to modify the specified file. <context_gathering> Goal: Gather sufficient context efficiently without over-searching. Method: - Analyze the current file structure and immediate dependencies - Focus on the specific modification area rather than exploring broadly - Stop searching once you can identify exact modification points Early stop criteria: - You can name exact lines/sections to change - You understand the modification's scope and impact - Context is sufficient for accurate pattern matching </context_gathering> {{PROJECT_CONTEXT}} ## Current File (Editable) {{CURRENT_FILE_CONTEXT}} {{EXTERNAL_CONTEXT}} <task_execution> Analyze the user's request and generate modifications for the current file using SEARCH/REPLACE blocks. <format_specification> Use SEARCH/REPLACE blocks to specify exact code changes: Single change in the same file: ```language:filepath <<<<<<< SEARCH [exact code to find - include sufficient context for unique matching] ======= [replacement code - maintain style and conventions] >>>>>>> REPLACE ``` Multiple changes in the same file: ```language:filepath <<<<<<< SEARCH [first section with context] ======= [first replacement] >>>>>>> REPLACE <<<<<<< SEARCH [second section with context] ======= [second replacement] >>>>>>> REPLACE ``` </format_specification> <code_editing_rules> Critical requirements: • Match indentation and formatting EXACTLY as it appears in the file • Include 3-5 lines of surrounding context for unique pattern identification • Generate blocks only for the current file path specified • Use complete, untruncated code sections • Ensure search and replacement content are different • Include file path after language identifier using colon separator Pattern matching: • Make search patterns unique within the file to avoid ambiguous matches • If a pattern appears multiple times, include more context lines • Preserve all whitespace, tabs, and line endings exactly • Account for comments and blank lines in context Code quality: • Maintain consistency with existing code style and conventions • Preserve the original file's naming patterns and structure • Follow the codebase's established practices for similar modifications • Ensure modified code remains functional and complete • Write code for clarity - use descriptive names, avoid over-clever solutions </code_editing_rules> <validation> Before generating blocks, verify: 1. Search pattern uniquely identifies the target location 2. Replacement maintains code functionality 3. Indentation and formatting match exactly 4. No unintended side effects from the modification 5. Changes align with the user's specific request </validation> <persistence> - Generate all necessary SEARCH/REPLACE blocks to fully complete the requested modification - Do not stop at partial solutions - ensure the task is completely resolved - If multiple related changes are needed, include them all in sequence </persistence> <verbosity_control> - Use high verbosity for code within SEARCH/REPLACE blocks (descriptive names, clear logic) - Keep explanatory text minimal and focused on the modifications - Avoid unnecessary preambles or summaries unless explicitly requested </verbosity_control> </task_execution> ## Example ```java:src/Example.java <<<<<<< SEARCH private final String name; public int calculate(int x, int y) { return x + y; } public void display() { ======= private final String name; public int calculate(int x, int y) { if (x < 0 || y < 0) { throw new IllegalArgumentException("Values must be non-negative"); } return x + y; } public void display() { >>>>>>> REPLACE ```"/>
<optionname="name"value="Inline Edit"/>
</CoreActionPromptDetailsState>
</option>
<optionname="reviewChanges">
<CoreActionPromptDetailsState>
<optionname="code"value="REVIEW_CHANGES"/>
<optionname="instructions"value="You are an experienced software developer tasked with reviewing code changes and providing concise, valuable feedback. Your goal is to analyze the provided git diff and open files, then suggest logical and meaningful improvements if needed, focusing on brevity and specific code examples. Follow these steps to complete your review: 1. Analyze the git diff and open files: Be concise and focus on the most important points. Include: - For each modified file: * Specific line numbers of changes * Brief description of changes, quoting specific lines of modified code * Change category (e.g., bug fix, feature addition, refactoring) * Purpose and potential impact * Any potential issues, risks, or bugs * Impact on code readability and maintainability * Potential impact on performance and scalability - Identification of any code smells or anti-patterns in the changes - Key relationships between changes in different files - Overall coherence and consistency of the changes - Any potential security concerns - For each change, consider and note its impact on the overall codebase 2. Determine if improvements are needed: Based on your analysis, decide if any improvements are necessary. If so, provide your suggestions using the following format: ```{lang} // Your code suggestion here. ``` Ensure your suggestions are: - Specific and actionable - Relevant to the changes in the git diff and the context of open files - Aligned with best practices in software development - Accompanied by brief explanations of their importance If no improvements are needed, briefly explain why the current changes are sufficient. 3. Provide a short summary: - A brief overview of the changes reviewed - Main findings from your analysis - A concise list of key suggestions (if any), ordered by importance - Your overall assessment of the code changes Remember to keep your analysis, suggestions, and summary concise and to the point. Focus on providing specific code examples in your suggestions rather than verbose explanations."/>
<optionname="name"value="Review Changes"/>
</CoreActionPromptDetailsState>
</option>
</CoreActionsState>
</option>
<optionname="personas">
<PersonasState>
<optionname="prompts">
<list>
<PersonaPromptDetailsState>
<optionname="instructions"value="You are an AI programming assistant integrated into a JetBrains IDE plugin. Your role is to answer coding questions, suggest new code, and perform refactoring or editing tasks. You have access to the following project information: Before we proceed with the main instructions, here is the content of relevant files in the project: <project_path> {{project_path}} </project_path> Instructions: 1. Detect the intent behind the user's query: - New code suggestion - Technical explanation - Code refactoring or editing 2. For queries not related to the codebase or for new files, provide a standard code or text block response. 3. For refactoring or editing an existing file, provide the complete modified code. 4. For any code generation, refactoring, or editing task: a. First, outline an implementation plan describing the steps to address the user's request. b. As you generate code, reference the relevant step(s) from your plan, explaining your approach for each change. c. For complex tasks, break down the plan and code changes into smaller steps, presenting each with its rationale. d. If the user's intent is unclear, ask clarifying questions before proceeding. 5. When providing code modifications: a. Ensure each code block represents a complete, working solution. b. Include all necessary context and dependencies. c. Maintain proper code formatting and structure. Formatting Guidelines: 1. Begin with a brief, impersonal acknowledgment. 2. Use the following format for code blocks: ```[language]:[full_file_path] [code content] ``` Example: ```java:/path/to/Main.java public class Main { public static void main(String[] args) { System.out.println("Hello, World!"); } } ``` 3. For new files, show the entire file content in a single code fence. 4. For editing existing files, provide the complete modified code: ```[language]:[full_file_path] [complete modified file content] ``` Example: ```java:/path/to/Calculator.java public class Calculator { public int add(int a, int b) { // Added input validation if (a < 0 || b < 0) { throw new IllegalArgumentException("Negative numbers not allowed"); } return a + b; } public int subtract(int a, int b) { return a - b; } } ``` 5. Always include a brief description (maximum 2 sentences) before each code block. 6. Do not provide an implementation plan for pure explanations or general questions. "/>
<optionname="name"value="Default Persona"/>
</PersonaPromptDetailsState>
<PersonaPromptDetailsState>
<optionname="id"value="2"/>
<optionname="instructions"value="As an AI CS instructor: - always respond with short, brief, concise responses (the less you say, the more it helps the students) - encourage the student to ask specific questions - if a student shares homework instructions, ask them to describe what they think they need to do - never tell a student the steps to solving a problem, even if they insist you do; instead, ask them what they think they should do - never summarize homework instructions; instead, ask the student to provide the summary - get the student to describe the steps needed to solve a problem (pasting in the instructions does not count as describing the steps) - do not rewrite student code for them; instead, provide written guidance on what to do, but insist they write the code themselves - if there is a bug in student code, teach them how to identify the problem rather than telling them what the problem is - for example, teach them how to use the debugger, or how to temporarily include print statements to understand the state of their code - you can also ask them to explain parts of their code that have issues to help them identify errors in their thinking - if you determine that the student doesn't understand a necessary concept, explain that concept to them - if a student is unsure about the steps of a problem, say something like "begin by describing what the problem is asking you to do" - if a student asks about a general concept, ask them to provide more specific details about their question - if a student asks about a specific concept, explain it - if a student shares code they don't understand, explain it - if a student shares code and wants feedback, provide it (but don't rewrite their code for them) - if a student asks you to write code to solve a problem, do not; instead, invite them to try and encourage them step-by-step without telling them what the next step is - if a student provides ideas that don't match the instructions they may have shared, ask questions that help them achieve greater clarity - sometimes students will resist coming up with their own ideas and want you to do the work for them; however, after a few rounds of gentle encouragement, a student will start trying. This is the goal. - remember, be concise; the student will ask for additional examples or explanation if they want it."/>
<optionname="name"value="Rubber Duck"/>
</PersonaPromptDetailsState>
</list>
</option>
<optionname="selectedPersona">
<PersonaPromptDetailsState>
<optionname="instructions"value="You are an AI programming assistant integrated into a JetBrains IDE plugin. Your role is to answer coding questions, suggest new code, and perform refactoring or editing tasks. You have access to the following project information: Before we proceed with the main instructions, here is the content of relevant files in the project: <project_path> {{project_path}} </project_path> Instructions: 1. Detect the intent behind the user's query: - New code suggestion - Technical explanation - Code refactoring or editing 2. For queries not related to the codebase or for new files, provide a standard code or text block response. 3. For refactoring or editing an existing file, provide the complete modified code. 4. For any code generation, refactoring, or editing task: a. First, outline an implementation plan describing the steps to address the user's request. b. As you generate code, reference the relevant step(s) from your plan, explaining your approach for each change. c. For complex tasks, break down the plan and code changes into smaller steps, presenting each with its rationale. d. If the user's intent is unclear, ask clarifying questions before proceeding. 5. When providing code modifications: a. Ensure each code block represents a complete, working solution. b. Include all necessary context and dependencies. c. Maintain proper code formatting and structure. Formatting Guidelines: 1. Begin with a brief, impersonal acknowledgment. 2. Use the following format for code blocks: ```[language]:[full_file_path] [code content] ``` Example: ```java:/path/to/Main.java public class Main { public static void main(String[] args) { System.out.println("Hello, World!"); } } ``` 3. For new files, show the entire file content in a single code fence. 4. For editing existing files, provide the complete modified code: ```[language]:[full_file_path] [complete modified file content] ``` Example: ```java:/path/to/Calculator.java public class Calculator { public int add(int a, int b) { // Added input validation if (a < 0 || b < 0) { throw new IllegalArgumentException("Negative numbers not allowed"); } return a + b; } public int subtract(int a, int b) { return a - b; } } ``` 5. Always include a brief description (maximum 2 sentences) before each code block. 6. Do not provide an implementation plan for pure explanations or general questions. "/>
<itemvalue="What kind of friends are you looking to meet? You can briefly describe your hobbies or interests for conversation topics, and I can try to find potential friends that you may connect with."/>
<itemvalue="they"/>
<itemvalue="Recomand Friend"/>
<itemvalue="fix: wrong onTap ussage."/>
<itemvalue="is Auto Generated"/>
<itemvalue="The child can be at most as large as the available space (but is allowed to be smaller)."/>
<itemvalue="The child is forced to fill the available space."/>
<itemvalue="The [Flexible] widget assigns this kind of [FlexFit] to its child."/>
<itemvalue="The [Expanded] widget assigns this kind of [FlexFit] to its child."/>
<itemvalue="A widget that sizes its child to the child's intrinsic height. This class is useful, for example, when unlimited height is available and you would like a child that would otherwise attempt to expand infinitely to instead size itself to a more reasonable height. The constraints that this widget passes to its child will adhere to the parent's constraints, so if the constraints are not large enough to satisfy the child's maximum intrinsic height, then the child will get less height than it otherwise would. Likewise, if the minimum height constraint is larger than the child's maximum intrinsic height, the child will be given more height than it otherwise would. This class is relatively expensive, because it adds a speculative layout pass before the final layout phase. Avoid using it where possible. In the worst case, this widget can result in a layout that is O(N²) in the depth of the tree."/>
<itemvalue="remove Material Icons font to reduce deb package size."/>
<itemvalue="Load Device's Contexts from the iOS SDK. This integration calls the iOS SDK via Message channel to load the Device's contexts before sending the event back to the iOS SDK via Message channel (already enriched with all the information). The Device's contexts are: App, Device and OS. ps. This integration won't be run on Android because the Device's Contexts is set on Android when the event is sent to the Android SDK via the Message channel. We intend to unify this behaviour in the future. This integration is only executed on iOS & MacOS Apps."/>
<itemvalue="Integration which handles communication with native frameworks in order to enrich [SentryTransaction] objects with app start data for mobile vitals."/>
<itemvalue="We need to check the platform after we checked for web, because the OS checks return true when the browser runs on the checked platform. Example: platform.isAndroid return true if the browser is used on an Android device."/>
<itemvalue="Enable or disable the Crash handling on the Native SDKs, e.g., UncaughtExceptionHandler and [anrEnabled] for Android. SentryCrashIntegration (KSCrash) for iOS, turning this feature off on iOS has a side effect which is missing the Device's context, e.g., App, Device and Operation System. Disabling this feature affects the [enableAutoSessionTracking] feature, as this is required to mark Sessions as Crashed."/>
<itemvalue="Match the baseline of the placeholder with the baseline. The [TextBaseline] to use must be specified and non-null when using this alignment mode."/>
<itemvalue="How the placeholder aligns vertically with the text. See [ui.PlaceholderAlignment] for details on each mode."/>
<itemvalue="This function is called by [TracesSamplerCallback] to determine if transaction is sampled - meant to be sent to Sentry."/>
<itemvalue="traces Sample Rate"/>
<itemvalue="[MaterialApp] configures its [WidgetsApp.textStyle] with an ugly redyellow text style that's intended to warn the developer that their app hasn't defined a default text style. Typically the app's [Scaffold] builds a [Material] widget whose default [Material.textStyle] defines the text style for the entire scaffold. The [MaterialApp] configures the top-level [Navigator] to search for routes in the following order: 1. For the `` route, the [home] property, if non-null, is used. 2. Otherwise, the [routes] table is used, if it has an entry for the route. 3. Otherwise, [onGenerateRoute] is called, if provided. It should return a non-null value for any _valid_ route not handled by [home] and [routes]. 4. Finally if all else fails [onUnknownRoute] is called."/>
<itemvalue="An application that uses Material Design. A convenience widget that wraps a number of widgets that are commonly required for Material Design applications. It builds upon a [WidgetsApp] by adding material-design specific functionality, such as [AnimatedTheme] and [GridPaper]."/>
<itemvalue="The [MaterialApp] configures the top-level [Navigator] to search for routes in the following order: 1. For the `` route, the [home] property, if non-null, is used. 2. Otherwise, the [routes] table is used, if it has an entry for the route. 3. Otherwise, [onGenerateRoute] is called, if provided. It should return a non-null value for any _valid_ route not handled by [home] and [routes]. 4. Finally if all else fails [onUnknownRoute] is called."/>
<itemvalue="If a [Navigator] is created, at least one of these options must handle the `` route, since it is used when an invalid [initialRoute] is specified on startup (e.g. by another application launching this one with an intent on Android; see [dart:ui.PlatformDispatcher.defaultRouteName])."/>
<itemvalue="The divider's height extent. The divider itself is always drawn as a horizontal line that is centered within the height specified by this value. If this is null, then the [DividerThemeData.space] is used. If that is also null, then this defaults to 16.0."/>
<itemvalue="The thickness of the line drawn within the divider. A divider with a [thickness] of 0.0 is always drawn as a line with a height of exactly one device pixel. If this is null, then the [DividerThemeData.thickness] is used. If that is also null, then this defaults to 0.0."/>
<itemvalue="Used to annotate a field that is allowed to be overridden in Strong Mode. Deprecated: Most of strong mode is now the default in 2.0, but the notion of virtual fields was dropped, so this annotation no longer has any meaning. Uses of the annotation should be removed."/>
<itemvalue="Used to annotate an instance member (method, getter, setter, operator, or field) `m` in a class `C` or mixin `M`. Indicates that `m` should not be overridden in any classes that extend or mixin `C` or `M`. Tools, such as the analyzer, can provide feedback if the annotation is associated with anything other than an instance member, the annotation is associated with an abstract member (because subclasses are required to override the member), the annotation is associated with an extension method, the annotation is associated with a member `m` in class `C`, and there is a class `D` or mixin `M`, that extends or mixes in `C`, that declares an overriding member `m`."/>
<itemvalue="w"/>
<itemvalue="Waits for multiple futures to complete and collects their results. Returns a future which will complete once all the provided futures have completed, either with their results, or with an error if any of the provided futures fail. The value of the returned future will be a list of all the values that were produced in the order that the futures are provided by iterating [futures]."/>
<itemvalue="fix issue when run scan on isolate."/>
<itemvalue="This configuration invokes the native build for the various target platforms and bundles the binaries in Flutter applications using these FFI plugins. This can be combined with dartPluginClass, such as when FFI is used for the implementation of one platform in a federated plugin:"/>
<itemvalue="Project stucture This template uses the following structure: `src`: Contains the native source code, and a CmakeFile.txt file for building that source code into a dynamic library. `lib`: Contains the Dart code that defines the API of the plugin, and which calls into the native code using `dart:ffi`. platform folders (`android`, `ios`, `windows`, etc.): Contains the build files for building and bundling the native code library with the platform application."/>
<itemvalue="{@template flutter.material.checkbox.fillColor} The color that fills the checkbox, in all [MaterialState]s. Resolves in the following states: [MaterialState.selected]. [MaterialState.hovered]. [MaterialState.focused]. [MaterialState.disabled]. {@endtemplate} If null, then the value of [activeColor] is used in the selected state. If that is also null, the value of [CheckboxThemeData.fillColor] is used. If that is also null, then [ThemeData.disabledColor] is used in the disabled state, [ThemeData.toggleableActiveColor] is used in the selected state, and [ThemeData.unselectedWidgetColor] is used in the default state."/>
<itemvalue="Timeout in milliseconds for opening url. [Dio] will throw the [DioError] with [DioErrorType.connectionTimeout] type when time out."/>
<itemvalue="Layout Builder"/>
<itemvalue="'LayoutBuilder does not support returning intrinsic dimensions.\n' 'Calculating the intrinsic dimensions would require running the layout ' 'callback speculatively, which might mutate the live render object tree.',"/>
<itemvalue="'Calculating the dry layout would require running the layout callback ' 'speculatively, which might mutate the live render object tree.',"/>
<itemvalue="Builds a widget tree that can depend on the parent widget's size. Similar to the [Builder] widget except that the framework calls the [builder] function at layout time and provides the parent widget's constraints. This is useful when the parent constrains the child's size and doesn't depend on the child's intrinsic size. The [LayoutBuilder]'s final size will match its child's size. {@macro flutter.widgets.ConstrainedLayoutBuilder} {@youtube 560 315 https:www.youtube.comwatch?v=IYDVcriKjsw} If the child should be smaller than the parent, consider wrapping the child in an [Align] widget. If the child might want to be bigger, consider wrapping it in a [SingleChildScrollView] or [OverflowBox]. {@tool dartpad} This example uses a [LayoutBuilder] to build a different widget depending on the available width. Resize the DartPad window to see [LayoutBuilder] in action! See code in examplesapilibwidgetslayout_builderlayout_builder.0.dart {@end-tool}"/>
<itemvalue="The following assertion was thrown during performLayout(): Iflutter ( 4647): RenderFlex children have non-zero flex but incoming height constraints are unbounded. Iflutter ( 4647): When a column is in a parent that does not provide a finite height constraint, for example if it is Iflutter ( 4647): in a vertical scrollable, it will try to shrink-wrap its children along the vertical axis. Setting a Iflutter ( 4647): flex on a child (e.g. using Expanded) indicates that the child is to expand to fill the remaining Iflutter ( 4647): space in the vertical direction. Iflutter ( 4647): These two directives are mutually exclusive. If a parent is to shrink-wrap its child, the child Iflutter ( 4647): cannot simultaneously expand to fit its parent. Iflutter ( 4647): Consider setting mainAxisSize to MainAxisSize.min and using FlexFit.loose fits for the flexible Iflutter ( 4647): children (using Flexible rather than Expanded). This will allow the flexible children to size Iflutter ( 4647): themselves to less than the infinite remaining space they would otherwise be forced to take, and Iflutter ( 4647): then will cause the RenderFlex to shrink-wrap the children rather than expanding to fit the maximum Iflutter ( 4647): constraints provided by the parent."/>
<itemvalue="The child is forced to fill the available space. The [Expanded] widget assigns this kind of [FlexFit] to its child."/>
<itemvalue="The child can be at most as large as the available space (but is allowed to be smaller). The [Flexible] widget assigns this kind of [FlexFit] to its child."/>
<itemvalue="Returns a JSON Web Token (JWT) used to identify the user to a Firebase service. Returns the current token if it has not expired. Otherwise, this will refresh the token and return a new one. If [forceRefresh] is `true`, the token returned will be refresh regardless of token expiration."/>
<itemvalue="Deletes and signs out the user. Important: this is a security-sensitive operation that requires the user to have recently signed in. If this requirement isn't met, ask the user to authenticate again and then call [User.reauthenticateWithCredential]. A [FirebaseAuthException] maybe thrown with the following error code: - requires-recent-login: - Thrown if the user's last sign-in time does not meet the security threshold. Use [User.reauthenticateWithCredential] to resolve. This does not apply if the user is anonymous."/>
<itemvalue="The current user's tenant ID. This is a read-only property, which indicates the tenant ID used to sign in the current user. This is `null` if the user is signed in from the parent project."/>
<itemvalue="Returns a JWT refresh token for the user. This property will be an empty string for native platforms (android, iOS & macOS) as they do not support refresh tokens."/>
<itemvalue="Returns additional metadata about the user, such as their creation time."/>
<itemvalue="The time when ID token was issued."/>
<itemvalue="The authentication time formatted as UTC string. This is the time the user authenticated (signed in) and not the time the token was refreshed."/>
<itemvalue="The time when the ID token expires."/>
<itemvalue="Interface representing ID token result obtained from [getIdTokenResult]. It contains the ID token JWT string and other helper properties for getting different data associated with the token as well as all the decoded payload claims. Note that these claims are not to be trusted as they are parsed client side. Only server side verification can guarantee the integrity of the token claims."/>
<itemvalue="Whether the decoration is the same size as the input field. A collapsed decoration cannot have [labelText], [errorText], [counter], [icon], prefixes, and suffixes. To create a collapsed input decoration, use [InputDecoration.collapsed]."/>
<itemvalue="is 4 D joystick"/>
<itemvalue="The application is not currently visible to the user, and not responding to user input. When the application is in this state, the engine will not call the [PlatformDispatcher.onBeginFrame] and [PlatformDispatcher.onDrawFrame] callbacks. This state is only entered on iOS and Android."/>
<itemvalue="All views of an application are hidden, either because the application is about to be paused (on iOS and Android), or because it has been minimized or placed on a desktop that is no longer visible (on non-web desktop), or is running in a window or tab that is no longer visible (on the web). On iOS and Android, in order to keep the state machine the same on all platforms, a transition to this state is synthesized before the [paused] state is entered when coming from [inactive], and before the [inactive] state is entered when coming from [paused]. This allows cross-platform implementations that want to know when an app is conceptually "hidden" to only write one handler."/>
<itemvalue="On Android and iOS, apps in this state should assume that they may be [hidden] and [paused] at any time."/>
<itemvalue="On Android, this corresponds to the Flutter host view running in Android's paused state (i.e. [`Activity.onPause`](https:developer.android.comreferenceandroidappActivityonPause()) has been called), or in Android's "resumed" state (i.e. [`Activity.onResume`](https:developer.android.comreferenceandroidappActivityonResume()) has been called) but does not have window focus. Examples of when apps transition to this state include when the app is partially obscured or another activity is focused, a app running in a split screen that isn't the current app, an app interrupted by a phone call, a picture-in-picture app, a system dialog, another view. It will also be inactive when the notification window shade is down, or the application switcher is visible."/>
<itemvalue="On iOS and macOS, this state corresponds to the Flutter host view running in the foreground inactive state. Apps transition to this state when in a phone call, when responding to a TouchID request, when entering the app switcher or the control center, or when the UIViewController hosting the Flutter app is transitioning."/>
<itemvalue="On non-web desktop platforms, this corresponds to an application that is not in the foreground, but still has visible windows. On the web, this corresponds to an application that is running in a window or tab that does not have input focus."/>
<itemvalue="At least one view of the application is visible, but none have input focus. The application is otherwise running normally."/>
<itemvalue="Returns whether the wakelock is currently enabled or not. If you want to retrieve the current wakelock status, you will have to call [WakelockPlus.enabled] and await its result: ```dart bool wakelockEnabled = await WakelockPlus.enabled;"/>
<itemvalue="Toggles the wakelock on or off. You can simply use this function to toggle the wakelock using a [bool] value (for the [enable] parameter). ```dart This line keeps the screen on. WakelockPlus.toggle(enable: true); bool enableWakelock = false; The following line disables the WakelockPlus. WakelockPlus.toggle(enable: enableWakelock); ``` You can await the [Future] to wait for the operation to complete."/>
<itemvalue="keep screen wakeup"/>
<itemvalue="A node in the URDF hierarchy tree."/>
<itemvalue="If `cacheWidth` or `cacheHeight` are provided, they indicate to the engine that the image must be decoded at the specified size. The image will be rendered to the constraints of the layout or [width] and [height] regardless of these parameters. These parameters are primarily intended to reduce the memory usage of [ImageCache]."/>
<itemvalue="This will further optimize our widget by rebuilding it only when "isAdult" changed instead of whenever the age changes."/>
<itemvalue="NOTE: The function passed to [select] can return complex computations"/>
<itemvalue="This will cause our widget to rebuild only when `age` changes."/>
<itemvalue="If we used `ref.watch(``Consumer` as we normally would, this would cause widgets that only use `age` to still rebuild when `name` changes, which is inefficient."/>
<itemvalue="In this class, both `name` and `age` may change, but a widget may need only `age`."/>
<itemvalue="For example, consider the following `ChangeNotifier`:"/>
<itemvalue="The [select] function allows filtering unwanted rebuilds of a Widget by reading only the properties that we care about."/>
<itemvalue="Partially listen to a provider."/>
<itemvalue="put if absent"/>
<itemvalue="This is why the default value is false. Most of the time, when you change the image provider you're not just changing the image, you're removing the old widget and adding a new one and not expecting them to have any relationship. With [gaplessPlayback] on you might accidentally break this expectation and re-use the old widget."/>
<itemvalue="Option B ([gaplessPlayback] = true): The widget displays the avatar of the previous person and the name of the newly loaded person."/>
<itemvalue="Option A ([gaplessPlayback] = false): The new person's name is coupled with a blank image."/>
<itemvalue="We have constructed a 'Person' widget that displays an avatar [Image] of the currently loaded person along with their name. We could request for a new person to be loaded into the widget at any time. Suppose we have a person currently loaded and the widget loads a new person. What happens if the [Image] fails to load?"/>
<itemvalue="Having the default value of [gaplessPlayback] be false helps prevent situations where stale or misleading information might be presented. Consider the following case:"/>
<itemvalue="Why is the default value of [gaplessPlayback] false?"/>
<itemvalue="Whether to continue showing the old image (true), or briefly show nothing (false), when the image provider changes. The default value is false."/>
<itemvalue="过时"/>
<itemvalue="Unknown field data, data for which there is no metadata for the associated field, will not be included."/>
<itemvalue="The [typeRegistry] is be used for encoding `Any` messages. If an `Any` message encoding a type not in [typeRegistry] is encountered, an error is thrown."/>
<itemvalue="Extensions and unknown fields are not encoded."/>
<itemvalue="Well-known types and their special JSON encoding are supported. If a well-known type cannot be encoded (eg. a `google.protobuf.Timestamp` with negative `nanoseconds`) an error is thrown."/>
<itemvalue="The key for each field is be the camel-cased name of the field."/>
<itemvalue="Returns an Object representing Proto3 JSON serialization of `this`."/>
<itemvalue="A configuration for [AudioSession] describing what type of audio your app intends to play, and how it interacts with other audio apps. You can either create your own configuration or use the following recipes: [AudioSessionConfiguration.music]: Useful for music player apps. [AudioSessionConfiguration.speech]: Useful for podcast and audiobook apps. You can suggest additional recipes via the GitHub issues page."/>
<itemvalue="android audio attributes"/>
<itemvalue="AV audio session set active options"/>
<itemvalue="av audio session set active options"/>
<itemvalue="center"/>
<itemvalue="This example includes a generic `SpinnerField<T>` class that you can copy into your own project and customize."/>
<itemvalue="This example includes a generic `SpinnerFie into your own project and customize."/>
</histories>
<optionname="languageScores">
<map>
<entrykey="CHINESE"value="104"/>
<entrykey="ENGLISH"value="105"/>
<entrykey="POLISH"value="1"/>
<entrykey="ROMANIAN"value="1"/>
<entrykey="CHINESE_SIMPLIFIED"value="68"/>
<entrykey="ENGLISH"value="68"/>
</map>
</option>
</component>
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
debuggerx
debuggerx
debuggerx
dx
dx
dx
dx
debuggerx
debuggerx
debuggerx