support.type.django.model not matching with some fields

[inancsevinc]

support.type.django.model is not matching with DateTimeField, IntegerField, PositiveIntegerField and URLField types.
It seems there are extra space characters preceding these names on line:
https://github.com/MattDMo/PythonImproved/blob/master/PythonImproved.tmLanguage#L49

[inancsevinc]

Actually this extra space char problem is not specific to the mentioned line, there are many similar cases in the PythonImproved.tmLanguage file.

[MattDMo]

@inancsevinc thanks for the bug report. I've tracked down to issue - I use AAAPackageDev to translate the XML-based .tmLanguage file to a YAML-based syntax, which is much easier to edit, then I save it back to the XML version. Unfortunately, spaces are inserted into long lines during one of those translation steps. So, support.type.django.model is supposed to look like this:

<dict>
    <key>match</key>
    <string>(meta|models)\.(Admin|AutoField|BooleanField|CharField|CommaSeparatedIntegerField|DateField|DateTimeField|DecimalField|EmailField|FileField|FilePathField|FloatField|ForeignKey|ImageField|IntegerField|IPAddressField|ManyToManyField|NullBooleanField|OneToOneField|PhoneNumberField|PositiveIntegerField|PositiveSmallIntegerField|SlugField|SmallIntegerField|TextField|TimeField|URLField|USStateField|XMLField)\b</string>
    <key>name</key>
    <string>support.type.django.model</string>
</dict>

but actually looks like this:

<dict>
    <key>match</key>
    <string>(meta|models)\.(Admin|AutoField|BooleanField|CharField|CommaSeparatedIntegerField|DateField|DateTimeField|DecimalField| EmailField|FileField|FilePathField|FloatField|ForeignKey|ImageField|IntegerField|IPAddressField|ManyToManyField| NullBooleanField|OneToOneField|PhoneNumberField|PositiveIntegerField|PositiveSmallIntegerField|SlugField| SmallIntegerField|TextField|TimeField|URLField|USStateField|XMLField)\b</string>
    <key>name</key>
    <string>support.type.django.model</string>
</dict>

which messes up the interpretation of the regexes and some of the fields don't get matched. However, now that I know about this, after building back to the tmLanguage format I just do a global search-and-replace for "| ", replacing it with "|", and things seem to be working now.

I'll be pushing out a new release in the next few minutes (v1.2.1), so please test it out and let me know if everything is working correctly now.

Thanks!
MattDMo

[MattDMo]

Addressed with 705ca99

[FichteFoll]

I just read about this in the package control update messages (and not on the AAAPackagDev repo).

May I ask how the corresponding yaml that creates the mal-formatted xml looks like? I suspect that you are using the > block syntax over multiple lines which inserts a space on every line break, by spec. In this case, however, you can simply fix it by using the (?x) override which will make the regular expression engine ignore all white spaces that are not preceeded by a backslash or inside a set.
(By using the | blocks syntax you can even preserve the newlines in the generated xml. Not like you'd look at that ever again now that yaml conversion exists, but just mentioning~.)

Example usage