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
We had the following suggestion: currently, if you click on a lens generated by makeLenses, it goes to the original TemplateHaskell call $(makeLenses ...) (from Control.Lens.TH). That's technically correct, since that's where the lens is defined, but almost always what you really want is the original record field definition instead. For example, in
data Foo = Foo { _bar :: Int }
$(makeLenses ''Foo)
...
... = ... bar ...
Clicking on bar in the last line should go to the original definition of _bar, rather than the call to makeLenses. The latter might not be close by the field, or it might be less convenient when there are many fields of a given record.
The text was updated successfully, but these errors were encountered:
If you emit the generates edge between the right entities, then the Kythe indexer will magically make the connection.. kythe/kythe@f7614b1 might be some inspiration, but this cleanly needs more clarification. I remember there was a good readme in the Kythe repo (maybe https://www.kythe.io/docs/schema/indexing-generated-code.html?)
We had the following suggestion: currently, if you click on a lens generated by
makeLenses
, it goes to the original TemplateHaskell call$(makeLenses ...)
(fromControl.Lens.TH
). That's technically correct, since that's where the lens is defined, but almost always what you really want is the original record field definition instead. For example, inClicking on
bar
in the last line should go to the original definition of_bar
, rather than the call tomakeLenses
. The latter might not be close by the field, or it might be less convenient when there are many fields of a given record.The text was updated successfully, but these errors were encountered: