Under Review
over 1 year ago

feature request: allow to spedify type checking level in the monkey.jungle file

I dislike that typechecking has to be enabled/disabled globally 

- For my existing projects I really don't want to (/I won't) go back and fix thousands of type check warnings

- If I start a new project I might use type checking

I propose to add a new keyword to the monkey.jungle file which adds a new keyword:

typechecking = [none | gradual | informative | strict]

Having this would enable you to choose on a per project basis if you want type checking on or not for that project.

peterdedecker
  • over 2 years ago in reply to FlowState

    On CLI I wouldn't mind this option. It allows a project to force it upon their developers. That means VScode, Eclipse (not sure if that would work reading your comments), etc would all play by the same rules.

  • over 2 years ago

    Yeah, not to state the obvious, but if you're using the CLI then anything goes, and you don't need this feature.

    You're right that OP may be talking about Eclipse, but then the first comment referred to VS Code settings, which is what prompted me to point out that you can already override type checking in VS Code on a per-workspace/folder basis.

    However, I went back to Eclipse and I noticed that there doesn't seem to be any options for the type-checking level (I checked for updates and hopefully updated to the latest available CIQ plugins). You can override command line options on both a global and per-project level, so the same argument applies.

    Also, Garmin mentioned that VS Code is their main dev environment now, and while Eclipse will continue to be supported, it won't be getting any new features. Seems that the specific option for type checking is one of those new features that got left out.

  • over 2 years ago in reply to FlowState

    Perhaps this is against eclipse or some other editor/framework? You are talking vscode, I'm talking CLI, OP is talking $some-other-flavor

  • over 2 years ago

    "Type checking does not need to be defined globally?"

    It doesn't. As noted, it can be defined on a per-workspace level or even per folder (for workspaces with multiple projects.)

  • over 2 years ago

    Type checking does not need to be defined globally? Or is this a bug against the vscode extension? I'm doing typechecking on a per project basis. Although I'm not against this feature as long as CLI args override the jungle file.

    Perhaps when included a default device would also be very welcome addition to be defined in the jungle file.