Emily
I’m using VueJS for the front-end of this project. File conventions are CamelCase, Elixir, snake_case.
Variable conventions differ too.
I’ve been following conventions, depending on language, but now code looks Frankenstein as a result, with inconsistent filenames & variable naming.
I can see this becoming a big problem when sharing variables between languages. How is the problem generally handled? What are the best practices here?
Do I mix & match conventions according to language? Or keep 1 universal convention for all modules in the project, regardless of language?
And if its the former, how is this problem handled when sharing variables between 2 languages?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
manukall
i’m following conventions in both parts. i use camel case variables in javascript and snake case in elixir.
to share data between elixir and javascript, you are going to use some form of api. this is the point where many transform then between camel case and snake case. if you’re going for absinthe/graphql for example, you will write your schema in elixir with camel case (
field :first_name) and your queries from javascript can use camel case (firstName) and it gets automatically matched.pierreabreup
@Emily @manukall Absinthe has an adapter to convert snake_case to camelCase ( absinthe/guides/adapters.md at main · absinthe-graphql/absinthe · GitHub ). I’m using this adapter and it works very well
The schema has to be snake_case to adapter works.
My project is a phoenix (version 1.4.) framework using absinthe (version 1.4.13) and absinthe_plug (version 1.4.6). To set up an absithe adapter, go to config.exs file and add the line below