Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrade to 0.19.1 broke examples that need specific versions of packages. #121

Open
pdamoc opened this issue Dec 4, 2019 · 2 comments
Open

Upgrade to 0.19.1 broke examples that need specific versions of packages. #121

pdamoc opened this issue Dec 4, 2019 · 2 comments

Comments

@pdamoc
Copy link
Contributor

pdamoc commented Dec 4, 2019

Example: https://ellie-app.com/5LFH95YJqpya1
pdamoc added a commit to pdamoc/ellie that referenced this issue Dec 5, 2019
@pdamoc
Changed install of dependencies to use elm-json, fixes ellie-app#121
0d74c0c
@dillonkearns dillonkearns mentioned this issue Feb 14, 2020
Merged
@yarus23
Copy link

yarus23 commented Feb 22, 2020

Is this the same error?
https://ellie-app.com/42ncDhHfsYxa1
It requires field 'error' that is not available in 6.0.1 version of composable form

@dillonkearns dillonkearns mentioned this issue Feb 29, 2020
Closed
@dillonkearns
Copy link

dillonkearns commented Mar 26, 2021 •
edited
Loading

It seems like if a given Ellie compiles, it should stay compiling. So it would make sense to lock in the specific dependencies' versions. Otherwise a major version bump to an Elm package can break an Ellie link that was previously compiling.

Is the current behavior intended, or is the intended behavior to keep a link locked in to the versions it was built with?

@jerith666 jerith666 mentioned this issue Dec 3, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pdamoc @dillonkearns @yarus23