perf(dotnet): optimize dictionary lookups in model Equals methods #664
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.
Optimize Dictionary Lookups in Model Equals Methods
Problem
The generated model Equals methods perform inefficient dictionary comparisons for
AdditionalProperties:This performs two dictionary lookups per key:
ContainsKey(kv.Key)- checks if key existsinput.AdditionalProperties[kv.Key]- retrieves the valueCodeQL Warning
Source: CodeQL static analysis on openfga/dotnet-sdk#156
Warning: "Inefficient use of ContainsKey and indexer"
Impact: Performance penalty on every equality check for models with AdditionalProperties
Solution
Use
TryGetValuewhich performs both operations in a single dictionary lookup:Changes
File:
config/clients/dotnet/template/modelGeneric.mustacheline 357Before:
After:
Impact
This optimization applies to all generated models with AdditionalProperties, including:
Testing
Verified that the generated code:
References
TryGetValueinstead ofContainsKey+ indexerFiles Modified
config/clients/dotnet/template/modelGeneric.mustacheSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.