Nah.. Don't worry about an edge case like me! That was just an extreme example. I can always just re-do my changes to a new fork of the new hotness... ((I hate client certificate authentication, not you, heh)).
I am just worried about fallout from users :( Changes to the File API needs to be NOISY. According to the stats from the plugin repository, it's one of the top downloaded plugins. O_o On 20/11/2013 1:43 AM, "Ian Clelland" <iclell...@google.com> wrote: > Oh, don't hate me, man :) > > If I can manage, I'll try to make FileTransfer *just work* with whatever > version of File you happen to have installed -- but that won't help you if > you want to keep your modified version of FileTransfer working with the new > version of File. > > It's unfortunate that it depends on the internals of File :( > > What are you doing to modify FileTransfer? If there's any way I can make > your job easier -- any hooks to expose, or extension points that should be > left in, let me know, and I'll see what I can do. > > Ian > > > On Mon, Nov 18, 2013 at 6:51 PM, Tommy Williams <to...@devgeeks.org> > wrote: > > > I'll hate you, but I guess I'll get over it (I have a plugin that is > > basically a modified fork of file-transfer.. . gonna be a pain updating > it > > now, heh). > > > > What happened to the suggestions for this all being a new plugin of some > > kind? Though plugins are versioned, an old version gets no bug fixes... > > On 19/11/2013 9:11 AM, "Brian LeRoux" <b...@brian.io> wrote: > > > > > Answers inline. > > > > > > > > > > Does FileTransfer implement any published standard, or is it our own > > API? > > > > > > > > Nope. > > > > > > > > > > > > > Does it make sense for FileTransfer to continue to use raw FileSystem > > > paths > > > > (and *not* go through File at all?) given that the File API will soon > > be > > > > returning only relative paths and filesystem:// URLs. > > > > > > > > Consistent w/ URL scheme makes sense to me but I'll let others chime > in > > > how this will break everything and our users will hate us. But > remember: > > > plugins are versioned! > > > > > >
