-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plug gazelle_cabal.ImportData in Resolve to allow both gazelle extensions to run in the same gazelle_binary #41
Closed
Closed
Changes from 6 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
afe761a
Plug gazelle_cabal.ImportData in Resolve to allow both gazelle extens…
GuillaumeGen ff90217
Add gazelle_cabal as a dependency in the example WORKSPACE
GuillaumeGen 8bdb276
Add gazelle_cabal in the test WORKSPACE
GuillaumeGen efd78dd
Add json package in stack_snapshot of tests
GuillaumeGen 2894e7a
Please buildifier
GuillaumeGen f2078a7
Reuse addNonHaskellModuleRule
GuillaumeGen a94dfc9
Clean r attributes based on newr
GuillaumeGen ba7e574
Update README
GuillaumeGen a7d8ffd
Handling of not existing yet BUILD.bazel files and cleaning of non ha…
GuillaumeGen 283dfcf
Add a test
GuillaumeGen bb8e1c8
Add the bazelrc.local file in the new test folder
GuillaumeGen 6dbbf31
Add Nix stuffs in WORKSPACE
GuillaumeGen bcf8101
Add RunImports and clean the tests
GuillaumeGen e02fbbc
Update WORKSPACE
GuillaumeGen 6958aae
Add enrichIx map to generate the dependencies between modules and nar…
GuillaumeGen 12ac604
Add missing setup_deps for ghc_922
GuillaumeGen 8281ff2
Gitignore generated file
GuillaumeGen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need some help understanding the flow. Is this case entered anytime a
haskell_binary/library/test
rule is updated or created bygazelle_cabal
?If so, how are
haskell_module
rules generated from this rule?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This case is entered whenever the
Resolve
function is called on rules that come from the same gazelle run (so rules where theimports
where constructed bygazelle_cabal
and not by the haskell libhimportscan
included ingazelle_haskell_modules
).Regarding the construction of
haskell_modules
rules, it is performed just like for other rules bysetNonHaskellModuleDeps
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code is calling
RunResolve
, which apparently is a duplicate of theResolve
callback ofgazelle_cabal
. Isn't that callback invoked bygazelle
implicitly?