INSERT_UPDATE Discount;code[unique=true];value;name[lang=en];name[lang=de];absolute[default=false]
;"5%";5;"5% Discount";"5% Rabatt";
;"7.5%";7.5;"7.5% Discount";"7,5% Rabatt";
;"10%";10;"10% Discount";"10% Rabatt";

Expected Behavior

name[lang=en] and name[lang=de] should be recognized as 2 columns.

Actual Behavior

name[lang=en] and name[lang=de] get recognized as one column.

Steps to Reproduce the Problem

1. Open a file with the content posted above

Specifications

• Extension Version: v0.2.3
• VSCode Version: 1.22.1
• Platform: Windows 10

Expected Behavior

Single quotes should not mark a string.

Actual Behavior

Single quote marks a string 😄 .

Specifications

• Version: v0.2.0
• Platform: Windows
• Subsystem: -

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Expected Behavior

No console errors

Actual Behavior

Console errors

Steps to Reproduce the Problem

1. Open "Help" -> "Toggle Developer Tools"
2. Go to "Console" tab
3. See error

Specifications

Due to the multi line comment entry being commented out in language-configuration.json, a trailing comma is present in the entry. This throws an error in the VS Code developer tools.

• Extension Version: ?
• VSCode Version: 1.24.0
• Platform: Mac OSX Sierra 10.12.6

Implement a formatting feature.
A formatted ImpEx should look like this:

INSERT Product ; code[unique=true] ; name[lang=de]
               ; 000001            ; Produkt

What you can see here is that every corresponding semicolon is aligned to each other. The "width" of a cell is defined by the max length of all values included plus the header.

Feature request

Shrink a modifier like @media[translator=com.domain.project.package.MyTranslator] to @media[MyTranslator] for better readability, but only visual without changing the real content.

• prove of concept

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

1. Added ""impex.editor.columnHighlighting.enable": true" to User Settings Preference file
2. Green Underscore says 'impex.editor.columnHighlighting.enable' is an Unknown Configuration Setting

Specifications

• Version: Code: Version 1.22.2 (1.22.2)
• Platform: MacOS Sierra 10.12.6
• Subsystem:

Feature Request

Highlight reference and keywords like &compopnent and non attribute columns like @media[translator=com.package.MyTranslator]

Expected Behavior

Comments should only be highlighted on the beginning of a line, anything else is not a comment.

Actual Behavior

Comments that start in the middle of a line like: ;56345;Name;LOT#3461, SAS;false;false;true; are highlighted as comment.

Steps to Reproduce the Problem

1. insert a # into a dataline

Specifications

• Version: v0.2.0
• Platform: Windows
• Subsystem: -

Expected Behavior

A semicolon in a string does not mark the next column, it is part of the string.

Actual Behavior

A semicolon in a string is recognized as marker for the next column.

Steps to Reproduce the Problem

1. put a string with a semicolon in it into a data line
2. column highlighting wont work correct

Specifications

• Version: v0.2.0
• Platform: Windows
• Subsystem: -