You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flow comment syntax is a continuing bother with prettier's formatting ( #709 ) and it sounds like its problems are very deep rooted, according to Christopher. Plus our continuing lack of Flow comments support because of a lack of upstream implementation mean that it just isn't... well, a good train to get on.
We're switching to Flow annotations - not Flow comments. This
gives documentation.js the ability to self-document without
JSDoc types and improves our compatibility with tools like
prettier.
Fixes#729. Fixes#709
We're switching to Flow annotations - not Flow comments. This
gives documentation.js the ability to self-document without
JSDoc types and improves our compatibility with tools like
prettier.
Fixes#729. Fixes#709
* build: Use Flow syntax without comments.
We're switching to Flow annotations - not Flow comments. This
gives documentation.js the ability to self-document without
JSDoc types and improves our compatibility with tools like
prettier.
Fixes#729. Fixes#709
Uh oh!
There was an error while loading. Please reload this page.
Flow comment syntax is a continuing bother with prettier's formatting ( #709 ) and it sounds like its problems are very deep rooted, according to Christopher. Plus our continuing lack of Flow comments support because of a lack of upstream implementation mean that it just isn't... well, a good train to get on.
This'd mean switching to real Flow annotations, which would then mean switching to using a tool to strip them out, and then potentially going all the way and producing a single bundle to save on startup time
What do folks think here: are Flow comments something we should dig into or something that would be wise to cut from scope?
The text was updated successfully, but these errors were encountered: