fix: map JSONSchema spec naming convention to snake_case when names from schema_extra are not found (#3766)

[charles-dyfis-net]

…when property names from schema_extra are not found.

Description

Address rejection of schema_extra values using JSONSchema spec-compliant key names by mapping between the relevant naming conventions.

Closes

Fixes #3766

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.34%. Comparing base (1e55ef3) to head (40b0b71).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3767      +/-   ##
==========================================
- Coverage   98.35%   98.34%   -0.02%     
==========================================
  Files         332      332              
  Lines       15460    15472      +12     
  Branches     2460     2464       +4     
==========================================
+ Hits        15206    15216      +10     
- Misses        112      113       +1     
- Partials      142      143       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[provinzkraut]

Thanks for reporting this and submitting a fix @charles-dyfis-net!

I'm not a fan of these regex based renaming solutions, as they can be tricky to maintain in some cases. I would prefer a more explicit approach. We could use dataclasses.field to provide an alias via metadata (e.g. multiple_of: float | None = field(metadata={"alias": "multipleOf"})

[charles-dyfis-net]

Thanks for reporting this and submitting a fix @charles-dyfis-net!

I'm not a fan of these regex based renaming solutions, as they can be tricky to maintain in some cases. I would prefer a more explicit approach. We could use dataclasses.field to provide an alias via metadata (e.g. multiple_of: float | None = field(metadata={"alias": "multipleOf"})

A wise objection -- going through the items one-at-a-time, there are some fixups (like schema_not) that the regex wouldn't have handled correctly.

[github-actions]

Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3767