-
Notifications
You must be signed in to change notification settings - Fork 11
New injections for forked elm packages #65
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
Draft
lydell
wants to merge
12
commits into
lamdera-next
Choose a base branch
from
lydell-upgrade-native
base: lamdera-next
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
43f9b29
New injections for forked elm packages
lydell 99c307e
Remove lamdera/containers injection
lydell 329e5aa
Add Browser.Navigation.Key support for serialization and migration li…
lydell 2434d1c
Make Browser.Navigation.Key work
lydell a41a5e6
Make the <pre> go away in `lamdera live`
lydell da2f7ad
As far as I understand, the code is correct, remove @TODO
lydell a0e1a5a
Merge branch 'lamdera-next' into lydell-upgrade-native
lydell 147a7c0
First step towards switcheroo
lydell aee782d
We have to use ~/.elm/0.19.2/ for IDE support
lydell d634ef8
Wire in maps of package replacements
lydell 2fd94a7
Add package replacement submodules
lydell 6b1b76a
Add TODO comments
lydell 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
Oops, something went wrong.
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’ve pointed these to my repos while developing, but before merging I think it makes sense to have forks in github.com/lamdera/
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’m not super concerned to fork, but was there a practical reason for it? Like are you worried we might end up needing a Lamdera specific variant, or just a cheap hedge to make now just in case?
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.
Maybe Simon doesn't want Lamdera to become dependent on his GitHub repositories? If so, maybe we could use Git subtrees instead of submodules. Then Simon's code would be copied into the Lamdera codebase, committed to the Lamdera repo. I used subtrees in some of my projects and found them to work well.
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.
Yeah, I feel slightly uneasy about Lamdera becoming dependent on my repos.
It’s not super “bad”, since the built binaries don’t depend on it, just the lamdera/compiler repo. And even there we are locked to specific commits of my repos, so if I accidentally change or remove a branch it won’t really break anything.
Anyhow, git subtrees might be better. I don’t know. I haven’t used them before. I might try that out after I’ve got the rest of the Haskell code in place.