sourcecred/.flowconfig

[ignore]

[include]

[libs]
flow-typed

[lints]

[options]
suppress_comment=\\(.\\|\n\\)*\\$ExpectFlowError
include_warnings=true

[strict]
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion 2018-02-16 22:32:24 +00:00			`[ignore]`

			`[include]`

			`[libs]`
			`flow-typed`

			`[lints]`

			`[options]`
Flow: enable `//$ExpectFlowError` (#315) As of this commit, adding the comment `//$ExpectFlowError` in flow-typed code asserts that the next line must cause a flow error. If it does, no error or warning is generated. If it does not, then this produces a flow warning, which is visible to developers running `yarn flow` and additionally causes travis to fail. Test plan: - As committed, `yarn travis` passes. - I added `//$ExpectFlowError` above some line of flow-checked code which does not currently throw an error. Afterwards, `yarn travis` failed (and a helpful message was displayed in console on running `yarn flow`) - I added the following bad code into one of our files: ```javascript //$ExpectFlowError const foo: string = 3; ``` As expected, `yarn flow` and `yarn travis` both passed. 2018-05-29 20:56:36 +00:00			`suppress_comment=\\(.\\\|\n\\)*\\$ExpectFlowError`
			`include_warnings=true`
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion 2018-02-16 22:32:24 +00:00
			`[strict]`