Added

Support for YAML-heavy/Python-light syntax that provides more structure without sacrificing expressiveness. This primarily affects the Response section of the http_request operation. See the updated examples in the readme.

Assets 2

0 Join discussion

05 Jun 00:19

maxgrinev-padb

v1.1.1

b385930

v1.1.1

Added

http_request operation now supports init section to define variables at the beginning of execution. For example, useful for implementing pagination. See an example at https://github.com/paloaltodatabases/sequor-integrations/blob/main/flows/bigcommerce_fetch_customers.yaml

Assets 2

0 Join discussion

03 Jun 18:06

maxgrinev-padb

v1.1.0

1da253c

v1.1.0

This release introduces compact syntax for http_request operations, making configurations more readable with YAML-based table definitions. See updated examples in the readme.

Added

Compact syntax for the http_request operation:
- Table definitions in YAML: you can now define tables in YAML instead of in the parser_expression return statement. Provides better readability and separation of concerns: Python code now handles only data mapping. The original return statement approach is still supported for flexibility (e.g., constructing schemas from response data)
- Simplified column definitions:
  - You can now use columns directly for table schema definitions without nesting them in model. The model syntax remains supported as models will expand beyond columns in future versions (e.g., data validation rules).
  - columns can now be defined using object compact syntax, for example, {id: "text", "first_name": "text", "last_name": "text"}
Added success_status: [...] support in the response section of http_request operation. Automatically raises an error if the response status code doesn't match the listed success codes.
def evaluate(context ...): line is now optional in _expression properties