Developing Custom Extensions Part 5 - parsing input data to get dynamic content

[Hyperbytes]

In this video we look at how we parse the output of our dynamic data sent through the module interface to reveal the underlying data.

we look at the methods outlines in this post.

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…

Wappler custom extensions part5 - parsing out inputs within .js

files used:
part5.zip (925 Bytes)