Suggestion: Add a version number in the header file

[solkennedy]

After I've installed card.io in my project, it would be helpful to be able to look up what version I'm running, especially after an email like you sent out today. Unfortunately, the current header doesn't include it.

Is there some other way to determine what version I have installed?

[dgoldman-pdx]

@plusbryan, good point!

Do you still have the release_notes.txt file that is part of every download? The version number does show up in there.

Also, you should be able to compare the date of your installed header files to the dates listed in the current version of release_notes.txt.

[josharian]

Hey @plusbryan, good to hear from you! CardIOPaymentViewController does expose +libraryVersion, although for a long time, the output from that was not particularly easy to interpret. That said, if you want to drop your libraryVersion in this issue, I'd be happy to correlate that to a version number for you...

[tooluser]

This issue just got closed, but what's the answer? Keep the packaging of the file around? Undesirable. . . is there a way regular humans can read +libraryVersion? Or did it get added to the header?

Thanks.

[dgoldman-pdx]

@tooluser, sorry! I closed this issue a bit too early.

By now, presumably @plusbryan's immediate issue has been resolved, one way or the other.

As of our next release (coming very soon!), we are adding the version number to the header files.

We might also add version number to the +libraryVersion output, but that's not happening this week.

[tooluser]

Right on, thanks! I emailed your support asking the same thing a few days ago!

On 8 Aug, 2013, at 16:46 , Dave Goldman notifications@github.com wrote:

@tooluser, sorry! I closed this issue a bit too early.

By now, presumably @plusbryan's immediate issue has been resolved, one way or the other.

As of our next release (coming very soon!), we are adding the version number to the header files.

We might also add version number to the +libraryVersion output, but that's not happening this week.

—
Reply to this email directly or view it on GitHub.