Seems like a consensus - I'll probably add a comment block at the top with a known token that you can replace (or two, for platform as well) - important for iOS version replacement since it is automated, not manual.
On Sat, Mar 24, 2012 at 12:42 AM, Jesse <[email protected]> wrote: > +1 > Also, the platform it was built for may make sense as well, so you can > easily open the file and isolate an issue of someone using an Android exec > in an iOS app .. ( which seems to happen a lot ) > > > > On Fri, Mar 23, 2012 at 11:04 PM, Brian LeRoux <[email protected]> wrote: > >> +1 >> >> On Fri, Mar 23, 2012 at 9:04 PM, Bryce Curtis <[email protected]> >> wrote: >> > I'm in favor of having the version inside - some integrators rename the >> JS >> > file, so having the version inside would be useful. >> > >> > It might be good to for corova-js init code to compare JS with native to >> > verify they are the same version - and alert the user if not. >> > >> > On Fri, Mar 23, 2012 at 6:03 PM, Shazron <[email protected]> wrote: >> > >> >> ... just like jQuery. Thoughts? Filename is enough? >> >> >> >> The way I did it from before in iOS was replace a known token inside >> >> the .js file with the version. >> >> >>
