feat: configure to get some info command metrics

[yaoyinnan]

Specify the index to get info xxx(info data, info stats) by configuring, instead of using info all.

Fixes: #1761

[cr-gpt]

It appears that the provided code patch is a configuration file or script with a list of boolean variables set to true or false. Without additional context, it is challenging to provide a comprehensive review.

However, based on what you've shared, here are some general suggestions:

1. Consistency: Ensure consistent formatting throughout the code. For example, decide whether to use uppercase or lowercase letters for boolean values and stick to that convention.

2. Variable Names: Consider using more descriptive variable names to enhance code readability. Instead of single-word variables like "server," "data," etc., provide names that indicate their purpose or usage.

3. Commenting: Add comments to clarify the purpose or functionality of certain variables or sections of the code, especially if they may not be immediately obvious to others who read your code.

4. File Ending: It seems that there is no newline character at the end of the file. Adding a newline at the end is generally recommended for better compatibility with various tools and editors.

Remember, a thorough code review should also consider the surrounding code, dependencies, and specific requirements. If you can provide more information about the code's purpose or any associated files, we can provide more targeted recommendations.

[cr-gpt]

Based on the code patch you provided, it appears to be a configuration file or settings that enable/disable certain features. Without additional context or the rest of the code, it is challenging to provide a comprehensive review. However, here are a few general observations:

1. Consistency: Ensure that the naming conventions and formatting used in this code patch are consistent with the existing codebase or the style guide.

2. Documentation: It would be helpful to provide comments or documentation explaining the purpose and usage of these settings.

3. Organization: Consider grouping related settings together or organizing them in a more structured manner for better readability and maintainability.

4. Error handling: If any of these settings have dependencies or require specific error handling, make sure to include appropriate checks or handling mechanisms.

5. Default values: Verify that the default values of these settings align with the intended behavior of the application.

6. Code reuse: Assess if any of these settings share common functionality or could be simplified by utilizing functions or classes.

Overall, without understanding the broader context of your application and its requirements, it's difficult to provide specific improvement suggestions. Please provide more information or share the related code if you need a more detailed review.

[AlexStocks]

怎么也调换下顺序，把 "log" 这种系统库放上面嘛

[cr-gpt]

This code appears to be a package related to configuration management. Here's a brief review of the code:

1. There are no apparent bugs in the provided code. However, without the overall context and usage of this code, it's difficult to determine if there are any functional or logical issues.

2. One potential improvement could be to handle error cases more effectively. Currently, when an error occurs while reading or parsing the TOML file, the code returns an error but does not provide any specific information about the error. It might be helpful to log or return a more detailed error message indicating the cause of the failure.

3. The use of the logrus package for logging is good practice to track the progress and display configurations.

4. The code structure looks reasonable, and the separation of concerns seems appropriate, with dedicated functions for loading the configuration and displaying it.

5. It's worth considering adding comments or documentation to explain the purpose and functionality of the code.

Overall, without further context, it appears to be a straightforward implementation of loading and displaying configurations from a TOML file.

[cr-gpt]

Overall, the code appears to be well-structured and readable. However, there are a few potential improvements and bug risks that can be addressed:

1. Consider defining the InfoConfig struct fields as pointers (*bool) instead of regular bool types if they are optional. This allows for better distinction between unset fields and false values.

2. In the LoadConfig() function, it would be useful to add error logging in case there is an error while reading or parsing the TOML file.

3. The readConfig() function could benefit from validating the presence of required fields in the TOML file before unmarshalling the data into the InfoConfig struct. This ensures that the TOML file matches the expected structure.

4. Ensure that InfoConfigPath is properly initialized with a valid path before calling LoadConfig() to prevent unexpected behavior.

5. In the CheckInfo() method, consider adding comments to explain the logic being performed. It helps with understanding the intent behind the code.

6. When printing the configuration in the Display() function, you may want to prefix each line with a consistent identifier like "[INFO]" to make it more clear that it's a log message.

These suggestions aim to enhance the clarity, maintainability, and robustness of the code.