For Those Using ChatGPT to Generate Wappler Extensions…

[mgaussie]

I do the same, I've found it to be very capable. Not always perfect but if you know what you are looking for when it's not working, it's easy to resolve.

Capability is only going to increase, too.

[updates]

Hi Wappler Community,

First of all, a big thank you to everyone who helped me get my extension up and running—it works perfectly now!

However, I’m facing a small issue that I hope someone can help me resolve. When I manually input the file path, for example:
public/telegram/telegram/2024-11-13/170aadba-67f2-4529-881a-ab3a0a97db03.mp4,
the extension detects the file correctly.

But if I use a dynamic path, like:
'public/telegram/' + file_name,
it doesn’t seem to find the file.

Does anyone have any suggestions on how I can fix this? I’d really appreciate your insights!

@kfawcett @Apple @Hyperbytes
Thank you in advance for your help!

[Hyperbytes]

Are you parsing the input before use?

Parse(), parseRequired() and parseOptional in custom module .js

This does not appear to be documented anywhere so hopefully this will clear up my questions and also act as a reference document. Here is my understanding and questions at the end. When creating custom extensions there are 3 main ways to parse dynamic data So, for example, if we have a a query called "query1" passed from a module via the HJSON interface from an input named "myquery" options, then options.myquery would return "query1". To obtain the actual data this must be parsed to get th…

[updates]

It worked perfectly. Thank you very much.
You're help on custom extension is invaluable !!

[Hyperbytes]

Thanks for the thank you! Very kind.

[updates]

You're hired !!