I know that aliases basically don't play any role when it comes to schema (which is what LS cares about), the local name should suffice. However we made a decision in the design of some LS components early on (admittedly with some tradeoffs) to perform exact match on the provider fields in resources and data source, as opposed to match just first step of the traversal.
That decision is not necessarily set in stone, but it would require quite a significant redesign and we'd probably just end up with different trade-offs.
This unblocks https://github.com/hashicorp/terraform-schema/pull/26 which in turn allows us to support 0.15 configurations and interpret them accurately.
I know that aliases basically don't play any role when it comes to schema (which is what LS cares about), the local name should suffice. However we made a decision in the design of some LS components early on (admittedly with some tradeoffs) to perform exact match on the
providerfields in resources and data source, as opposed to match just first step of the traversal.That decision is not necessarily set in stone, but it would require quite a significant redesign and we'd probably just end up with different trade-offs.