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
I thought we did this, but perhaps it got lost when translating the rulerefs provider to Rego.
Looks like we're showing the "rule" (variable) icon for all symbols here. We should use the function type for functions, and perhaps use "reference to rule" and "reference to function" rather than the current "rule ref" text.
The text was updated successfully, but these errors were encountered:
Had a look at this and indeed, the rulerefs Rego provider is only ever handed the refs as strings, so there's no way it can determine which of them are rules, functions or whatnot. This also means that the metadata annotations that we'd previously use to show documentation for the refs when asked for no longer are there.
We've got all of this data in the (Go) caller, so it wouldn't be hard to pass it to the provider. It'll be a lot more data to process though, so when we do that we'll need to be careful about checking the overhead / penalty we'll get from doing so.
I thought we did this, but perhaps it got lost when translating the
rulerefs
provider to Rego.Looks like we're showing the "rule" (variable) icon for all symbols here. We should use the function type for functions, and perhaps use "reference to rule" and "reference to function" rather than the current "rule ref" text.
The text was updated successfully, but these errors were encountered: