Search results

The XML docs describe mode literals with inconsistent casing (e.g., "AsStored" vs the actual default "asStored"). Standardize the documented literals to match what the API expects/produces to avoid confusing clients.

Status: Open.

#12 In David-H-Afonso/GamesDatabase.Api;

· David-H-Afonso opened on Feb 24, 2026

<code>effectiveConfig</code> can become null if the request JSON includes <code>globalConfig: null</code> or a per-game entry with a null value (System.Text.Json can deserialize nulls into reference-typed properties). That will lead to a 500 via <code>ApplyExportString</code>. Add request validation (and/or null-coalescing fallback) so null configs result in a 400, or default to a new config instance.

Status: Open.

#10 In David-H-Afonso/GamesDatabase.Api;

· David-H-Afonso opened on Feb 24, 2026

Per-game overrides are keyed by <code>record.Name</code> using the default (case-sensitive) dictionary comparer, but the rest of the import matches games case-insensitively. This makes overrides easy to miss due to casing differences. Normalize keys (e.g., build a case-insensitive lookup after deserialization) or compare using a consistent case.

Status: Open.

#9 In David-H-Afonso/GamesDatabase.Api;

· David-H-Afonso opened on Feb 24, 2026

The API response includes <code>details = ex.Message</code> on a 500. This can leak internal information (e.g., parsing errors, DB/provider errors) to clients. Consider returning a generic message and logging the exception details server-side (or only include details in Development).

Status: Open.

#8 In David-H-Afonso/GamesDatabase.Api;

· David-H-Afonso opened on Feb 24, 2026

If <code>configJson</code> is invalid JSON, <code>JsonSerializer.Deserialize</code> will throw and you’ll return a 500. Treat malformed config as a client error: catch <code>JsonException</code> and return 400 with a clear message (and also validate that <code>config.GlobalConfig</code> isn’t null after deserialization).

Status: Open.

#7 In David-H-Afonso/GamesDatabase.Api;

· David-H-Afonso opened on Feb 24, 2026

<code>ExportFullDatabase</code> doesn’t populate <code>CriticProvider</code> (and will export it as an empty column), while <code>ImportFullDatabase</code> expects/uses <code>record.CriticProvider</code>. This causes data loss on export→import roundtrips; populate <code>CriticProvider</code> (and any other persisted game fields you intend to roundtrip) in the <code>FullExportModel</code> creation here.

Status: Open.

#6 In David-H-Afonso/GamesDatabase.Api;

· David-H-Afonso opened on Feb 24, 2026