axelson
Scenic Core Team
I’m curious how many minor Elixir versions library authors generally try to support. I’m thinking that a good default is 3 minor versions which will equate to roughly 1.5 years (and is the approach mentioned in Library builders: What versions of Elixir to support? When to stop supporting older Elixir versions? - #3 by Qqwy). And of course the previous versions of a library are still available for users that are unable to upgrade elixir for some reason.
Trending in Discussions
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
New
The obligatory hello world thread!
Who are you and where are you from? :stuck_out_tongue:
New
I want to open this thread for you all to discuss and help those who really like Ash but are still hesitant to use it in a real project. ...
New
I was working on an Ecto migration and I needed a timestamp. So, for the nth time, I looked up the different data types for timestamps, a...
New
Fly’s CEO posted this recently - Turn And Face The Strange · The Fly Blog
It says that Fly is going all-in on sprites, which is a worry ...
New
We’re evaluating API mocking tools for OpenAPI-based projects and would love to hear what other teams are using.
We’re particularly inte...
New
Is there a word for the ~> symbol used in Version strings?
Do you also just call it a Squiggle Arrow™ ?!
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Aludel - LLM Evaluation Workbench
Aludel is an embeddable Phoenix LiveView dashboard for evaluating and comparing LLM prompts across mult...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
@axelson I’m also a fan of supporting basically 2 major versions of a lib that have different Elixir version reqs. Eg: some library named Foo that has:
It depends a bit on how important new Elixir features are to your app.
dimitarvp
I’d support anything I could but it depends how easy it would be to just copy-paste the functions from newer Elixir releases to a dedicated
Compatmodule namespace. I am entertaining the idea for a long time and I think it can work out fine.Having said that, I’d aim for current version plus 2 versions behind, e.g. 1.12, 1.11 and 1.10.
stratacast
Mind if I hijack the thread to get some clarity? Say 1.9-1.11 your library works, but 1.12 breaks it. In your example, I could create a 1.6.x branch and specify it as tested for 1.12, but how would that work for something like hex.pm? It would only display the latest version of my lib, wouldn’t it? And would that be left up to the developer to see that they’d have to downgrade their version?