dbsimmons64

dbsimmons64

Hi All

Just started looking at Hologram and think it has huge potential. Is there a list of what does, and doesn’t work when converting from Elixir to JavaScript. I was looking to validate that a form field was a valid number and had the following

elixir

case Integer.parse(params.event.value) do

      {int, _} -> int

      :error -> :error

end:


```

When running the code I get the following error in the console:

runtime.entry.js:364 Uncaught HologramBoxedError: (FunctionClauseError) no function clause matching in Integer.count_digits/2

The following arguments were given to Integer.count_digits/2:

    # 1
    "1"

    # 2
    10


I’m assuming this is because Integer.parse doesn’t yet convert to JavaScript. Of course I could be completely wrong and this is a silly error on my part.

cheers

Showing Posts 1 to 4

BartOtten

BartOtten

deleted: Too fast, too furious.

dbsimmons64

dbsimmons64 OP

Is that me or you :slight_smile:

bartblast

bartblast

Creator of Hologram

Hey @dbsimmons64,

Elixir functions are transpiled automatically to JavaScript by Hologram. However, at the very bottom layer, they use Erlang functions which need to be ported by hand to JavaScript. The detailed process is described here: Hologram Elixir -> JS compilation - #6 by bartblast

If some Erlang function isn’t yet ported, an error with details about the missing function is displayed in the browser console. However, that’s not what you encountered here.

The error you’re seeing with Integer.count_digits/2 was due to problems with bitstring segments handling in the client-side implementation. However, even after fixing that initial bitstring handling issue, you would have eventually encountered errors about missing Erlang function ports that Integer.parse/2 depends on. So there were actually two layers of problems: first the bitstring patterns handling, and then missing Erlang functions underneath.

Good news:

I’ve just released v0.6.3 that fixes the client-side support of Integer.parse/2. Both the bitstring handling issues and the missing Erlang function dependencies have been resolved, so your code should work now after updating.

Current project stage:

At this stage of the project, if something doesn’t work it’s usually a small thing and I typically fix it within 24 hours - just like with your issue!

Going forward:

I completely agree - we need more transparency about which Erlang functions are missing. I’ve been thinking recently about creating some initiative to help me port the rest of the functions. The process is actually quite simple, especially with the help of AI tools (it’s a perfect use case for them), but it’s time-consuming for me as I’m juggling many other aspects of the project like new features, core functionality, etc.

If you’re interested in helping with Hologram development, porting these Erlang functions would be the perfect way to contribute! Each function is relatively straightforward to implement, and I’m happy to review pull requests and provide guidance.

dbsimmons64

dbsimmons64 OP

Thanks so much @bartblast for the detailed explanaition. I’ll take a look at the link you’ve provided to see if I can better understand the process (if so I’d love to help out). Cheers.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Damirados
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews