wachulski / merlin Goto Github PK

When param A has default someVal and for environment E1 also someVal then YAML should contain only entry for default value. If default value is non empty and E1 is empty, then YAML must contain E1 specific value set to - E1: '', to differenciate from default value (otherwise YAML interpretation would conclude default value for E1 which is not same as for Excel setup).

For a parameter with an undefined configuration value for environment A, excel driver produces a redundant cell for that environment (empty). This leads to serializing back to YAML with that parameter configured for A environment like: - A: ''. This differs from the original YAML.

Reads configuration from Excel source (e.g. xls file) and builds a model in memory.

A parameter without any configured value (either default or environment related) should be allowed in YAML config.

myParam:
  value:
    - Test: 15
    - default: 20

will put '' (empty) to cell representing Local environment, should be same as default (20). This is the consequence of a new semantics of missing environment values introduced with #11.

Produces Excel xls output in Excel 2003 XML format.

Parse YAML sources (e.g. files) and create the configuration model in memory.

Produces YAML output

This implies writing public API doc. Otherwise DLL won't be built.

Writing abc to a target file out.txt containing 123456 results in out.txt abc456. Initial content must be erased at first.

Create and publish a nuget package v 1.0

Now either default value or at least one environment value mapping must be specified (non-empty). This prohibits existence of non-filled parameters. Pls make it possible, ie. only param name should be required.

Add support of environments ie. each configuration parameter value can be specified for a given environment.

When listing values in config-params.yml, everything works fine if default comes last:

 __<administrateCustomerId>__:
    value:
    - __TemplateName__: __CustomerId__
    - A11: 210000
    - A14: 230000
    - AM7: 270000
    - AM8: 280000
    - BETA2: 14
    - Developer: 1
    - US8: 980000
    - Verification: 14
    - default: 240000

When default is not the last option, the specific values keep working, but the default value does not turn up in the web.config:

 __<administrateCustomerId>__:
    value:
    - __TemplateName__: __CustomerId__
    - A11: 210000
    - A14: 230000
    - AM7: 270000
    - AM8: 280000
    - BETA2: 14
    - Developer: 1
    - US8: 980000
    - default: 240000
    - Verification: 14

Wrong end result in web.config (this one is from AM3):

<!-- General customer settings -->
<add key="administrateCustomerId" value="" />  <!-- Which customer can add or edit customers -->

C# analysis + code coverage. Use sonarqube.com integration with GitHub