Flow error when a custom generator's dependencies contains a non-flow-degen import about flow-degen

[gyrfalcon]

Just wanted to update this here, the project where I was running into this issue has been updated to use app-specific Type and Import values and the flow errors are gone.

I also updated the branch linked above with changes that get flow to pass. If desired I can turn that into a PR so there's a test for this.

[LoganBarnett]

We had some discussion about this. I think this can be a little confusing. The CustomImport: string that we see all over the generators is basically saying that CustomImport is constrained by string and not a type alias of string. This allows us to do string things with CustomImport, but since it's an externally provided type, it could be further constrained by other things.

As far as a fix goes, @gyrfalcon will need to remove CustomImport (and possibly CustomType), and instead use the application-specific types that CustomImport and CustomType are meant to represent. This means in the custom generator the type params should be stripped from customDegen.

I'll leave this open for now - I feel like the actionable thing to do here is to document the expectations, and, I think, correct the type signature used in the custom generator example.

[LoganBarnett]

Retroactive tests for existing behavior (and docs to go with it?!) are always appreciated!

[LoganBarnett]

The related pull request (#14) has been merged so this should be addressed now. Closing.