This stack of individually reviewable commits fully decouples the platform-specific weblet implementation from the platform-agnostic daemon, turning it into a Node.js-specific unconfined worklet.
Removing the allegëd type from formula identifiers entirely increased the urgency of fixing #1921. The new weblet architecture does not require a special web bundle type or any of the other weird coupling issues they have with wildcard subdomains. That refactor is bundled with this fix.
Also motivated by weblets, eval formulas now receive both $cancelled and $id endowments. The $id endowment is necessary for weblets to recognize their own access token, a path constructed from a prefix of their own formula identifier. I’ve renamed the cancelled endowment because I could not in good conscience claim the global id, and this made the two names consistent.
Security Considerations
Scaling Considerations
Documentation Considerations
Testing Considerations
Compatibility Considerations
Upgrade Considerations
[ ] Includes *BREAKING*: in the commit message with migration instructions for any breaking change.
closes: #1921
Description
This stack of individually reviewable commits fully decouples the platform-specific weblet implementation from the platform-agnostic daemon, turning it into a Node.js-specific unconfined worklet.
Removing the allegëd
typefrom formula identifiers entirely increased the urgency of fixing #1921. The new weblet architecture does not require a special web bundle type or any of the other weird coupling issues they have with wildcard subdomains. That refactor is bundled with this fix.Also motivated by weblets,
evalformulas now receive both$cancelledand$idendowments. The$idendowment is necessary for weblets to recognize their own access token, a path constructed from a prefix of their own formula identifier. I’ve renamed thecancelledendowment because I could not in good conscience claim the globalid, and this made the two names consistent.Security Considerations
Scaling Considerations
Documentation Considerations
Testing Considerations
Compatibility Considerations
Upgrade Considerations
*BREAKING*:in the commit message with migration instructions for any breaking change.NEWS.mdfor user-facing changes.