You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use statement itself is properly resolved to the definition, but when referencing it somewhere, you get a reference with the same name but the path of the current module.
This eventually leads to options.context.symbols.query(ctx.doc, 'mcdoc', '::java::data::predicate::Predicate') being resolved as a union of (::java::data::predicate::LootCondition | [::java::data::predicate::LootCondition]) which itself is not a valid mcdoc reference.
use super::loot::LootCondition
type Predicate = (LootCondition | [LootCondition])
dispatch minecraft:resource[predicate] to Predicate
The text was updated successfully, but these errors were encountered:
This is intentional, so when you Ctrl+click LootCondition it goes to the use statement first, and Ctrl+click again goes to the actual definition. The use statement introduces the referenced symbol into the current scope under a new symbol path and is a valid reference.
The use statement itself is properly resolved to the definition, but when referencing it somewhere, you get a reference with the same name but the path of the current module.
This eventually leads to
options.context.symbols.query(ctx.doc, 'mcdoc', '::java::data::predicate::Predicate')
being resolved as a union of(::java::data::predicate::LootCondition | [::java::data::predicate::LootCondition])
which itself is not a valid mcdoc reference.The text was updated successfully, but these errors were encountered: