Closed atombrenner closed 11 months ago
atombrenner
commented
1 year ago @lovell Any thoughts on this? I published a beta package from my fork and it works quite well for me. I think we could publish a 2.0.0-rc1 release candidate and see if people like it.
lovell
commented
1 year ago @papandreou Hi Andreas, as someone who maintains packages that depend on exif-reader, would you be interested in reviewing this semver major change?
atombrenner
commented
11 months ago @devongovett , @lovell can I do anything else, so that we can merge and publish a version?
lovell
commented
11 months ago All good, thank you Christian. If no one has any objections I can tag the latest as v2.0.0 and publish to npm.
lovell
commented
10 months ago @atombrenner Thanks again. Would you be able to start the deprecation process for the @types/exif-reader package? https://github.com/DefinitelyTyped/DefinitelyTyped#removing-a-package
atombrenner
commented
10 months ago @lovell,@akwodkiewicz Started the deprecation process, see https://github.com/DefinitelyTyped/DefinitelyTyped/pull/66885
My proposal for #29
Use the canonical tag names from the Exiv2 project. This gives us tag names that are aligned with the Exif standard. It enables generation of more specific typescript types. It will also prevent potential wrong information as the former version defined a few duplicate tag names.
This is a major version change, as group and tag names will change. See below:
Duplicate Tag Names
Changed Tag Names
New Tag Names
Non standard Tag Names (removed)
A sampling of those values on https://exiftool.org/TagNames/EXIF.html indicates that they are either offsets to vendor specific IFDs or are not part of any IFD (basicly undocumented on exiftool)