Add is_tt2() like is_json() to database, constraint on atevdef.template
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Today we give users few or no tools to test the TT2 markup they may enter when editing the template field of Action Trigger Event Definitions.
This could be a start to addressing that. It's just a database-level constraint around a function called is_tt2() that simply verifies that a given template compiles. It doesn't run the result, and it can't tell you whether your variables are defined or anything like that, and specific error messages don't bubble up to users using the staff client admin interfaces to edit templates or anything like that.
But it is at least a quick resource at the database level that will let you know when you haven't balanced all your IFs with ENDs, and that sort of thing.
Open to improvements, or merging as-is with proper testing/sign-off.
Changed in evergreen: | |
status: | New → Triaged |
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
Changed in evergreen: | |
milestone: | 2.4.0-rc → 2.5.0-alpha |
no longer affects: | evergreen/2.5 |
Changed in evergreen: | |
milestone: | 2.5.0-m1 → 2.5.0-m2 |
Changed in evergreen: | |
milestone: | 2.5.0-m2 → 2.5.0-alpha1 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha1 → 2.5.0-alpha2 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha2 → 2.5.0-beta1 |
Changed in evergreen: | |
milestone: | 2.5.0-beta1 → 2.5.0-rc |
Changed in evergreen: | |
milestone: | 2.5.0-rc → 2.5.1 |
Changed in evergreen: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in evergreen: | |
milestone: | 2.5.2 → none |
tags: | added: actiontrigger wishlist |
tags: | removed: wishlist |
Changed in evergreen: | |
assignee: | Galen Charlton (gmc) → nobody |
Of course what this really needs is a pgtap unit test!