Problem of parser when analyzing data from an external API

[Mr.Rubi]

When requesting a server action directly, everything works fine and there are no problems:

If I access the same server action from another application using an API action:

I will get the data correctly:

However, on the frontend there are problems with the analysis of expressions used in the repeat:

Repeat is displayed correctly, but the expressions inside it do not work. However, the application where the data comes from uses the same frontend, and no problems arise. Only if the frontend is used in a third-party application and the data comes through the API, there is a problem with parsing.

Why does such a problem arise and how can it be solved? I would be grateful for any idea.

[Apple]

Have you checked if your secondary front-end loads the same Javascript Wappler libraries?

[bpj]

Can you paste the code for where you are using the data on the page of your secondary project? I suspect you haven’t accounted for the repeat array being inside the extra ‘data’ property in the returned JSON from the API action

[Mr.Rubi]

@Apple and @bpj thanks guys for the help. How many times have I been convinced of the usefulness of brainstorming. I racked my brain for many hours, rechecked the expressions many times, and then checked the API many times. And having found nothing, I got into a dead end. And the problem was elementary. But if I hadn’t asked, I might not have noticed her for a long time. @Apple was right. The second application was really missing an important libraries, namely dmxFormatter.js. Apparently when I copied the code from the main application, I missed it. It is for this reason that all logical expressions did not work, because data formatting is used everywhere there.

Thanks again guys!

[Apple]

@Mr.Rubi

I racked my brain for many hours, rechecked the expressions many times, and then checked the API many times. And having found nothing, I got into a dead end. And the problem was elementary.

Looks like I just had a similar moment

Wappler, did you break environment variables?

So, the question is, Wappler, did you break environment variables? NodeJS + Wappler 4.6.3 (spoiler: YES) edit: no db.json: # cat app/modules/connections/db.json { "name": "db", "module": "dbconnector", "action": "connect", "options": { "client": "postgres", "connection": { "host": "{{$_ENV[DB_HOST]}}", "port": "{{$_ENV[DB_PORT]}}", "user": "{{$_ENV[DB_USER]}}", "password": "{{$_ENV[DB_PASS]}}", "database": "{{$_ENV[DB_NAME]}}" } } } Startu…

Happy to help! I guessed it was missing libraries due to the "Formatter (...) doesn't exist for type array", which is a kind of error which I think I saw when handling custom formatters