- This topic has 10 replies, 6 voices, and was last updated 8 years, 1 month ago by
support-piotr.
-
AuthorPosts
-
Fedor LosevParticipantexport const environment = { production: false, name: 'local' };
move the caret after the
{
brace on the first line and press Enter. This will result in an incorrect brace inserted after the line break:export const environment = { } production: false, name: 'local' };
There are may cases with similar scope behavior, e.g.
if(){
.The workaround is to press Enter when the caret is on the second line, but it is not convenient.
-
This topic was modified 8 years, 1 month ago by
Fedor Losev.
-
This topic was modified 8 years, 1 month ago by
Fedor Losev.
May 12, 2017 at 2:37 am #522521
support-tonyKeymasterFedor,
I’ve been able to replicate the problem and have raised a bug for the development team to investigate. We’ll let you know when a fix is out. Sorry for the inconvenience.
May 13, 2017 at 6:33 pm #522640
Fedor LosevParticipantNote in the frequent case of transforming single line definition to multi line there is no any workaround, we always have to correct the mess after the generator:
const x = { a: 1 };
const y = { };
Result:
const x = { }a: 1 }; const y = { } };
Expected:
const x = { a: 1 }; const y = { };
May 15, 2017 at 9:54 am #522804
support-swapnaModeratorFedor,
Thank you for the details. I have added them to the bug report and the dev team is looking into it.
–Swapna
MyEclipse SupportMay 22, 2017 at 11:09 am #523786
andrei-ivanovParticipantIs there a public roadmap somewhere for Webclipse?
May 23, 2017 at 6:21 am #523902
support-swapnaModeratorAndrei,
Sorry, there is no roadmap page available for Webclipse.
–Swapna
MyEclipse SupportMay 29, 2017 at 1:56 pm #524723
Brian FernandesModeratorAndrei / Fedor,
We’ve put out a prerelease of the 2017 CI 6 release, which addresses the typing issue. To get the pre-release build, please follow the instructions in this thread: https://www.genuitec.com/forums/topic/webclipse-angular-ide-prerelease-stream/
Do let us know if your issue is fixed by the prerelease stream, so we can ensure the final 2017 CI 6 release correctly addresses your problems.
May 29, 2017 at 2:45 pm #524731
andrei-ivanovParticipantSeems to work fine now, thank you ?
June 1, 2017 at 2:38 am #525173
Fedor LosevParticipantYep, seems fixed.
June 3, 2017 at 5:22 pm #525458
Fedor LosevParticipantThere is still case if there is no closing brace.
const x = { a:1
If caret is positioned before
a
and ENTER is pressed, this results inconst x = { }a:1
Similar frequent case
let x: Observable<string>; x.map( s => s );
If one comes to convert it to scoped body instead of
s
after=>
, the intuition is to put opening brace before s and press ENTER. This results inx.map( s => { }s );
Putting closing brace is a good thing, but moving lambda or member definition after the brace is not handy.
-
This reply was modified 8 years, 1 month ago by
Fedor Losev.
June 5, 2017 at 3:10 am #525556
support-piotrParticipantFedor,
Thanks for reporting this. We will work on further improvement of auto-addition of braces in the next release – CI7.
-
This topic was modified 8 years, 1 month ago by
-
AuthorPosts