No autocomplete offered for nested properties when key starts with number

[zoran995]

Describe the bug

The language server in vscode doesn't offer autocomplete for nested object properties when the key starts with a number.
For example, when I type {{ address.2country. }} properties name and code are not offered, but if I replace 2country with country in the object definition, it will properly show the suggestions.

Source

custom object definition

[
  {
    name: 'address',
    access: {
      global: true,
      parents: [],
      template: []
    },
    properties: [
      {
        name: 'city',
        return_type: [
          {
            type: 'string',
            name: ''
          }
        ],
        access: {
          global: false,
          parents: [],
          template: []
        }
      },
      {
        name: '2country',
        return_type: [
          {
            type: 'country_data',
            name: ''
          }
        ],
        access: {
          global: false,
          parents: [],
          template: []
        }
      }
    ],
    return_type: []
  },
  {
    name: 'country_data',
    access: {
      global: false,
      parents: [],
      template: []
    },
    properties: [
      {
        name: 'name',
        return_type: [
          {
            type: 'string',
            name: ''
          }
        ],
        access: {
          global: false,
          parents: [],
          template: []
        }
      },
      {
        name: 'code',
        return_type: [
          {
            type: 'string',
            name: ''
          }
        ],
        access: {
          global: false,
          parents: [],
          template: []
        }
      }
    ]
  }
]

Expected behaviour
Autocomplete suggestions should be offered for elements that are starting with any alphanumeric characters.

Actual behaviour
Autocomplete suggestions aren't offered when the key starts with a number.

Debugging information

• OS [e.g. Windows, Mac, Linux]
• OS Version
• Theme Check Version [e.g. 0.1.0]

Additional context
Any ideas on how to fix this?

[graygilmore]

In the near future with all themes moving to Liquid's new strict parser this will not be valid Liquid. The lookup will need to be {{ address['2country'] }}. With that in mind I'm going to close this but we'll chat about how we may want to support this in the future..