[UTY-2389] CodeWriter v2: minimum feature set (1/3)

[paulbalaji]

Description

The minimum feature set of CodeWriter v2 such that CodeGenerationLib can make full use of it.

Information about the CodeWriter v2 classes

ICodeBlock

• a unit of code that can be turned into an indented string

ScopeBlock : ICodeBlock

• a CodeBlock with scope + indentation implemented

ScopeBody : ScopeBlock

• contains helpers for writing code that is found in functions

CustomScopeBlock : ScopeBody

• a generic scope with optional declaration

LoopBlock : ScopeBody

• a scope with mandatory declaration for defining loops

ScopeBodyList : ICodeBlock

• a grouping of scoped bodies

IfElseBlock : ScopeBodyList

• a unit representing if/elseif/else code

TryCatchBlock : ScopeBodyList

• a unit representing try/catch/finally code

InitializerCodeBlock : ICodeBlock

• a helper to write initializers

Text : ICodeBlock

• plaintext

TextList : ICodeBlock

• a grouping of text to be on consecutive lines

Pending work before merging

• changelog
• regenerate & validate test-project code
• run playground

Tests

• ensuring generated code still compiles (buildkite)
• check generated code diff to ensure any changes are only whitespace trivia

[improbable-prow-robot]

Corresponding JIRA ticket: https://improbableio.atlassian.net/browse/UTY-2389

[zeroZshadow]

This could be a lovely switch statement

[zeroZshadow]

Lots of blocks create their own indent string, while most blocks will share a similar indent string.
We should have a helper to get this indent string, which caches the string for certain indentation levels.
With indentation level 0 hard coded to string.Empty

[jamiebrynes7]

Add link to this PR in the changelog then

[jessicafalk]

overall lgtm, one question regarding loops: seems like the loop block covers foreach / for / while, but what about do { .. } while (...)

[paulbalaji]

overall lgtm, one question regarding loops: seems like the loop block covers foreach / for / while, but what about do { .. } while (...)

I didn't find a need for it when porting across our current templates, but it's something that could be added in later should we need it