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
This is caused by the indenting of /** multi-line */ blocks, it was matching the 4-space-indent and being considered code. This included the last line */ so it didn't "exit" the comment properly.
For testing, I duplicated everything in the comments file and put it inside a class so it was indented enough. After the fix, the only change was the bit we wanted:
@devoncarew FYI. It's possible I introduced this with one of the earlier changes, so if you don't have them you might not need this. Best way is to type stdio and then Go-to-Def on it, and see whether most of the file is green/comment.
I've scanned through a few of the large Flutter files and made sure there are no other obvious instances of anything like this, nor any files that are comments till the end.
Activity
DanTup commentedon Apr 24, 2019
This is caused by the indenting of
/** multi-line */blocks, it was matching the 4-space-indent and being considered code. This included the last line*/so it didn't "exit" the comment properly.For testing, I duplicated everything in the comments file and put it inside a class so it was indented enough. After the fix, the only change was the bit we wanted:
@devoncarew FYI. It's possible I introduced this with one of the earlier changes, so if you don't have them you might not need this. Best way is to type
stdioand then Go-to-Def on it, and see whether most of the file is green/comment.I've scanned through a few of the large Flutter files and made sure there are no other obvious instances of anything like this, nor any files that are comments till the end.
Update comment sample for #1635