Morgan :)
Morgan :)
Throws should be caught, too :)
Thanks for filing. The problem with allowing reading previous outputs is that it makes the build no longer reproducible: you can get a different result every time you build, because...
Ah, for serialization compatibility? I think the right way to think of that is as an input. For example proto buffer definition files require you to write a "tag number"...
> Some from of persisted state would be cool though. > > I could think of some use-cases for it. For example, one generator could list all the DB tables...
> > so you could just require people to write them everywhere :) > > This generator was created specifically to remove the need for annotations on every type and...
> How about having `buildStep.writeAsString` accept an optional `signature` or `digest` parameter? Then, in future builds, we could use something like `buildStep.readCachedAsString(id, signature)` to retrieve a file from a previous...
> > I'm not sure I follow, how would the builder know the signature? > > The build framework simply stores the signature provided by the builder. Each builder implementation...
Hmmmmmm. How do you identify the user-created file, does it have a particular name, particular content?
Then I think the right answer is just a normal `.dart` generator that simply decides to do nothing for most files :) This is somewhat inefficient, but no more so...
One question, what does your `dart:io` implementation currently do?