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
While building reflex-dom 0.6.3.1 in nixpkgs I get:
reflex-dom> [3 of 3] Compiling Reflex.Dom.Location.Platform ( src/Reflex/Dom/Location/Platform.hs, dist/build/Reflex/Dom/Location/Platform.o, dist/build/Reflex/Dom/Location/Platform.dyn_o )
reflex-dom>
reflex-dom> src/Reflex/Dom/Location/Platform.hs:16:38-72: error:
reflex-dom> Not in scope: ‘Reflex.Dom.Location.popHistoryState’
reflex-dom> NB: the module ‘Reflex.Dom.Location’ does not export ‘popHistoryState’.
reflex-dom> Suggested fix:
reflex-dom> Perhaps use one of these:
reflex-dom> data constructor ‘Reflex.Dom.Location.HistoryItem’ (imported from Reflex.Dom.Location),
reflex-dom> data constructor ‘Reflex.Dom.Location.HistoryStateUpdate’ (imported from Reflex.Dom.Location)
reflex-dom> |
reflex-dom> 16 | module Reflex.Dom.Location.Platform (Reflex.Dom.Location.popHistoryState) where
reflex-dom> |
Reflex.Dom.Location.popHistoryState should be exported from reflex-dom-core. But the newest release of reflex-dom-core 0.8.0.0 does not export it. The change that moved the function from reflex-dom to reflex-dom-core happened in #453 after the reflex-dom-core release 0.8.0.0 but before the last reflex-dom release.
The text was updated successfully, but these errors were encountered:
Thanks for the report. reflex-dom-core 0.8.1.0 has been released with those functions, and reflex-dom 0.6.3.1 has been revised on hackage to reflect this version dependency.
While building reflex-dom 0.6.3.1 in nixpkgs I get:
Reflex.Dom.Location.popHistoryState
should be exported from reflex-dom-core. But the newest release of reflex-dom-core 0.8.0.0 does not export it. The change that moved the function from reflex-dom to reflex-dom-core happened in #453 after the reflex-dom-core release 0.8.0.0 but before the last reflex-dom release.The text was updated successfully, but these errors were encountered: