Cannot declare multiline function about civet HOT 8 CLOSED

Thanks Daniel, really helpful! Read the readme like 5 times but I missed that :D

+1 for optional assignment, I never understood why it's not a thing in typescript and it's always a big bummer
conditional assignment is also very nice!

Civet has a really, really bright future 🌈

from civet.

Hmmm, I have VSC set to 4 spaces for indentation.
If I use 2 spaces, it works.

3 spaces creates this weird code:

let bla = (one: string, two: string) => {
  return  console.log(one)  
  (console.log(two))
}

from civet.

@zolomatok Currently the indentation in Civet is hard coded at two spaces and most things will work correctly with that.

I'm currently working on an update to allow for arbitrary/deeper nesting. I'll let you know when it's out.

from civet.

Ah, great, thanks Daniel!
Is there an official or unofficial roadmap for Civet?
I'm very curious to get a glimpse of what state the language is in at the moment.
Seems like there's a ton of work that already been done, I mean barring a few hiccups, the language already seems to have feature parity with coffee.

from civet.

@zolomatok The short term goal is to get to 97%-99% compatibility with Coffee2 using the "civet coffeeCompat" directive prologue. I'm running tests on the CoffeeScript codebase and fixing issues as I find them.

Then it's making sure there is a clear incremental migration path from some unfortunate Coffee inconsistencies (for in/of/from names are swapped, not precedence). Adding some extra features &blocks, increasing TypeScript support... and the big one of having a really nice VSCode LSP.

This section of the Readme is a pretty good place to check: https://github.com/DanielXMoore/Civet#things-removed-from-coffeescript especially the TODOs near the bottom.

from civet.

Also possibly of interest is a Discord server which originally had the goal of adding TypeScript features to CoffeeScript but it has a #civet channel where Daniel announces new releases and features and such, and we discuss direction.

from civet.

@zolomatok This should be fixed now (at least your specific example). Let me know if you find other cases that don't work.

from civet.

Works great, thank you!

from civet.