Suggestion database wrongly reports reexported_in for Constructor entries.
#7671
Unanswered
vitvakatu
asked this question in
Work In Progress - Engine
Replies: 1 comment 1 reply
-
|
You're right, |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Issue
While working on #7468, I was asked to insert
Boolean.TrueandBoolean.Falsetypes in dropdowns without unnecessaryBooleanprefixes. After further investigation, it proved to be impossible with the current suggestion database.Technically, we should be able to see that
Boolean.Trueconstructor is reexported by theStandard.Basemodule and, as we havefrom Standard.Base import all, neither importing nor fully qualified name is required. But the suggestion database has areexported_infield set for the Type and all its Constructors. So we can't distinguish whether the Constructor was reexported or only its type was.Example
Boolean.Trueis reexported to theStandard.Base. It is shown in thereexported_infield:{ "name": { "content": "True" }, "in": "Standard.Base.Data.Boolean", "reexported_in": "Standard.Base" }Standard.Base.Data.Regression.Model.Logarithmic:{ "name": { "content": "Logarithmic" }, "in": "Standard.Base.Data.Regression", "reexported_in": "Standard.Base" }As you can see, we can't distinguish between
Boolean.TrueandLogarithmic, and therefore can't useTruewithout theBooleanprefix.Beta Was this translation helpful? Give feedback.
All reactions