Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

wzalazar
Copy link
Contributor

This PR introduces:

Better compatibility when is instrumenting the code. Project with Typescript code has a lot of issues when flow can't instrument the code.

  • Adds the option staticType with default value flow, it can be flow or typescript
  • Unit test

@wzalazar wzalazar mentioned this pull request Jul 20, 2018
5 tasks
@coreyfarrell
Copy link
Member

I'm wondering if we could just use #205 to provide this? I'm not too keen on the idea of having two options control plugins, it seems like it could become confusing.

@wzalazar
Copy link
Contributor Author

wzalazar commented Aug 2, 2018

@coreyfarrell

yeah, we can do it in the #205. regarding static types, it's important to know that plugin flow and typescript don't work together and we should somehow mention to the users. For this reason, I added this option separately

@coreyfarrell
Copy link
Member

Now that I've merged #205 I'm not sure what you want to do with this? Maybe this could be solved by documenting the conflict?

@wzalazar
Copy link
Contributor Author

yes, mention it in the documentation is enough

@JaKXz
Copy link
Member

JaKXz commented Aug 28, 2018

I think we should close this and have the doc PR separately. Thanks again for your contribution :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants