question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Flow v.0.84.0 explicit inexact objects

See original GitHub issue

We will be releasing flow 0.84.0 this week, which includes the ... syntax for inexact objects (for more info, see the blog post). AFAIK, flow-typed doesn’t require babel support to land before we can start upgrading the syntax here. I’m aiming to have the flow-upgrade command ready end of week to help you guys move through this as quickly as possible.

I’m opening this issue as a request for help, as I am not able to see this through myself. I imagine a script can be written with the following logic:

for each flow-typed library definition:
  copy the folder to one for flow v0.84.0
  run `flow-upgrade` in that new folder

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:10 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
villesaucommented, Oct 24, 2018

Ok, that’s good to know! 2 weeks should be enough for us to migrate the libdefs to new format. Eaxct by default change is great BTW! 😃

1reaction
jbrown215commented, Oct 24, 2018

flow-upgrade is blocked on the new flow parser being deployed, which should happen today or tomorrow. As soon as that happens, I’ll make sure everything is ok with flow-upgrade and release.

I’ve noticed a few bugs in the tools flow-upgrade relies on, so I’m fixing those as I find them. A notable such example is that recast doesn’t traverse opaque types.

The good news is that this change is not breaking-- we are still parsing anything with just curly braces {} as inexact objects, so you have at the very least 2 weeks from when the new version of flow is released to make sure this gets done.

Edit: bug blocking flow-upgrade https://github.com/benjamn/ast-types/pull/290

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to upgrade to exact-by-default object type syntax | Flow
After you upgrade all of those tools, try putting explicit inexact object types {...} manually in a few spots in your codebase and...
Read more >
Read more - GitHub
This can cause errors if you are passing a function or inexact objects when an indexed object is expected. * Flow now processes...
Read more >
Exploring Causal Relationships in Visual Object ... - CiteSeerX
Causal relationships can often be found in visual object tracking between the motions of the camera and that of the tracked object. This...
Read more >
DIFFICULTTOREAD INMICROFICHE PR.ODUCTS. - OSTI.gov
codes do not provide such derivatives as part of a flow so- ... v. • .. s s pline level or an implicit...
Read more >
A THREE-DIMENSIONAL MULTI-BLOCK NEWTON-KRYLOV ...
inexact -Newton method with an approximate-Newton method for startup. ... Another division of CFD flow solvers can be found between implicit and explicit...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found