fix chart handler

[iceljc]

PR Type

Other

---

Description

• Standardize project configuration using solution-level variables

• Replace hardcoded values with MSBuild property references

• Add package generation and documentation settings

---

Diagram Walkthrough

flowchart LR
  A["Hardcoded Values"] --> B["MSBuild Variables"]
  B --> C["Standardized Config"]
  C --> D["Package Generation"]

Loading

File Walkthrough

Relevant files

Configuration changes

BotSharp.Plugin.ChartHandler.csproj Standardize project configuration with MSBuild variables  src/Plugins/BotSharp.Plugin.ChartHandler/BotSharp.Plugin.ChartHandler.csproj Replace hardcoded net8.0 with $(TargetFramework) variable Add MSBuild properties for version, package generation, and documentation Remove ImplicitUsings setting and add LangVersion configuration Set output path to solution packages directory +7/-3

---

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Missing Variables The project now depends on several MSBuild variables that must be defined at the solution level. If these variables are not properly defined, the build will fail or produce unexpected results. <TargetFramework>$(TargetFramework)</TargetFramework> <Nullable>enable</Nullable> <LangVersion>$(LangVersion)</LangVersion> <VersionPrefix>$(BotSharpVersion)</VersionPrefix> <GeneratePackageOnBuild>$(GeneratePackageOnBuild)</GeneratePackageOnBuild> <GenerateDocumentationFile>$(GenerateDocumentationFile)</GenerateDocumentationFile> <OutputPath>$(SolutionDir)packages</OutputPath> Build Impact Removing ImplicitUsings may break existing code that relied on implicit using statements. The codebase should be verified to ensure all necessary using statements are explicitly declared. <TargetFramework>$(TargetFramework)</TargetFramework> <Nullable>enable</Nullable> <LangVersion>$(LangVersion)</LangVersion>

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Add fallback for undefined variable Using a variable for TargetFramework without defining a fallback value could cause build failures if the variable is undefined. Consider adding a fallback value or condition to ensure the project can build independently. src/Plugins/BotSharp.Plugin.ChartHandler/BotSharp.Plugin.ChartHandler.csproj [4] -<TargetFramework>$(TargetFramework)</TargetFramework> +<TargetFramework Condition="'$(TargetFramework)' == ''">net8.0</TargetFramework> +<TargetFramework Condition="'$(TargetFramework)' != ''">$(TargetFramework)</TargetFramework> Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that an undefined $(TargetFramework) variable can cause build failures and proposes a standard MSBuild condition to provide a fallback, improving the project's build robustness.	Medium
More