Skip to content

row 159: re-export MACRO_DOOR beside door (busbar #1469 A1) - #35

Closed
MattJackson wants to merge 3 commits into
devfrom
row159-macro-door-reexport
Closed

MattJackson wants to merge 3 commits into
devfrom
row159-macro-door-reexport

Conversation

@MattJackson

Copy link
Copy Markdown
Contributor

Ruling A1 for busbar #1469: busbar's generated linked tables name <entry module>::MACRO_DOOR for every linked row, and plugin_door! emits MACRO_DOOR only in the module that invokes it. This re-exports MACRO_DOOR beside door in this plugin's entry module.

The re-export needs busbar #1449 (MacroDoor), so the busbar pin moves 7263f4e61b -> 08d4d7c501 (busbar dev head): .busbar-ref, manifests, workflow refs, and the busbar entries of Cargo.lock only.

…-ref, manifests, Cargo.lock, workflow refs

The pin moves to busbar dev, which carries #1449 (MacroDoor, plugin_door!'s MACRO_DOOR).
busbar's generated linked tables name <entry module>::MACRO_DOOR for every linked row; plugin_door!
emits it only in the module that invokes it, so the entry module re-exports it beside door.
- [patch] busbar-contract (the www.github.com spelling) moves to 08d4d7c501 with its Cargo.lock source line; it was still at the old pin.
- declares.json drops the contract_abi range, as busbar-release plugin render at 08d4d7c501 writes it (busbar plugin-gates declares refuses a stated range).
- The Cargo.toml / deny.toml comments name the new pin.
@MattJackson

Copy link
Copy Markdown
Contributor Author

Superseded by #34 (door-root, ee19184): per ruling (A), /status row 195, the logic crate's only public item is fn door(), so the A1 MACRO_DOOR re-export falls away and the migration is folded into #34.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant