You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deployable =
The engine is ordinary Apex: it can seed sandboxes and scratch orgs, but it counts toward your org's Apex character limit and needs its own production test coverage (as do your custom Providers and value expressions).
@IsTest-only =
None of that burden, but no seeding.
A stripped "deployable build" alongside the @istest one is technically possible — the sandbox-seeding branch prototypes it.
Should XFTY 4.0 ship a deployable (non-@IsTest) distribution?
Yes — seeding is worth the coverage burden
0%
No — keep it @IsTest-only and simple
0%
Ship both — an @IsTest build and a stripped deployable one
0%
Not sure — need to understand the trade-off better
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Deployable =
The engine is ordinary Apex: it can seed sandboxes and scratch orgs, but it counts toward your org's Apex character limit and needs its own production test coverage (as do your custom Providers and value expressions).
@IsTest-only =
None of that burden, but no seeding.
A stripped "deployable build" alongside the @istest one is technically possible — the sandbox-seeding branch prototypes it.
0 votes ·
All reactions