docs(readme): fix namespace references#54
Conversation
Update using statements in code examples to use the correct namespaces
|
| using QRCoder.Core.Generators; | ||
| using QRCoder.Core.Renderers; |
There was a problem hiding this comment.
🚩 Bilingual docs not updated alongside README
The PR updates import statements in README.md code examples from using QRCoder.Core; / using SkiaSharp; to using QRCoder.Core.Generators; / using QRCoder.Core.Renderers;. However, the equivalent code examples in docs/en-US/usage-guide.md:54-55 and docs/pt-BR/guia-de-uso.md:54-55 still use the old imports (using QRCoder.Core; and using SkiaSharp;). The AGENTS.md DO rules include "Documentação bilíngue (pt-BR + en-US)", and these docs now show different (and likely incorrect) import statements compared to the README. This pre-existing inconsistency is now amplified by the PR — the README is correct while the docs remain stale.
Was this helpful? React with 👍 or 👎 to provide feedback.
| using QRCoder.Core; | ||
| using SkiaSharp; | ||
| using QRCoder.Core.Generators; | ||
| using QRCoder.Core.Renderers; |
There was a problem hiding this comment.
📝 Info: Removal of using SkiaSharp; is safe due to var usage
The Quick Start example previously had using SkiaSharp; which was replaced by using QRCoder.Core.Renderers;. This is safe because the code example uses var for all SkiaSharp types (e.g., using var bitmap = qrCode.GetGraphic(10); where the return type is SKBitmap). No SkiaSharp type names are referenced explicitly anywhere in the README code examples. If a user wanted to extend these examples with explicit SkiaSharp types (like SKEncodedImageFormat), they would need to add using SkiaSharp; themselves — but the examples as written are self-consistent.
Was this helpful? React with 👍 or 👎 to provide feedback.



Update using statements in code examples to use the correct namespaces