Skip to content

fix(composite): preserve raw APEX ValueConv precision - #384

Closed
swackhamer wants to merge 0 commit into
mainfrom
codex/fix-composite-apex-precision
Closed

fix(composite): preserve raw APEX ValueConv precision#384
swackhamer wants to merge 0 commit into
mainfrom
codex/fix-composite-apex-precision

Conversation

@swackhamer

Copy link
Copy Markdown
Collaborator

Summary

  • Split APEX ValueConv from PrintConv so Composite inputs receive raw seconds and f-numbers rather than formatted strings such as 1/152 or 4.7.
  • Keep the existing EXIF display output unchanged by applying PrintConv only at CLI-formatting time.
  • Add regression coverage proving the Composite path retains the raw 2^-7.25 shutter value.

Verification

  • cargo fmt --all -- --check
  • cargo test --lib composite::
  • cargo test --lib exiftool_compat::

@swackhamer
swackhamer marked this pull request as ready for review August 2, 2026 02:22
@swackhamer
swackhamer enabled auto-merge (squash) August 2, 2026 02:22
@swackhamer
swackhamer force-pushed the codex/fix-composite-apex-precision branch from 57101c5 to d10aa02 Compare August 2, 2026 07:42
auto-merge was automatically disabled August 2, 2026 07:42

Pull Request is not mergeable

@swackhamer swackhamer closed this Aug 2, 2026
@swackhamer
swackhamer force-pushed the codex/fix-composite-apex-precision branch from d10aa02 to 45de0df Compare August 2, 2026 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant