Git Product home page Git Product logo

flow-guide's People

Contributors

amilajack avatar iredchuk avatar nwshane avatar peterschussheim avatar rpunkfu avatar wpcarro avatar y-temp4 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

flow-guide's Issues

PR: Adding Documentation for eslint-plugin-flowtype-errors

Working on a plugin that reports flow errors as eslint errors:

Demo:
ESLint Flow Demo

Note: In this demo, I am using atom with the packages 'linter' and 'linter-eslint'

Would a PR for updating the documentation, regarding this plugin, be welcome?

Add some runtastic guidelines (best practise)

We are currently gaining a lot of experience while using FlowType for internal libs, so we soon will be able to add some best-practises guidelines in here (beside the tutorial).

This will cover some topics like...

  • Where should I put my type definitions?
  • When and where should I export my type definitions?
  • How do we expose type definitions / declarations to our other codebase?
  • How do we deliver libdefs of our own modules?

Lesson 00/03 should use assert.strictEqual

Tell me if I'm wrong, but I assume that the test at the bottom of the tutorial/00-basics/03-dynamic-object-keys.js should fail? At the moment, the test passes because it compares '1000' to 1000 using the equal comparison operator rather (assert.equal) instead of the strict equality operator (assert.strictEqual).

Let me know if this is right and I'll submit a pull request changing this to assert.strictEqual.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.