perms: move perms.go into looprpc #930
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overall plan and context: lightninglabs/lightning-node-connect#113 (comment)
The Lightning Node Connect (LNC) WASM client currently imports both
looprpcand the entireloopmodule to accessperms.go. This creates problems becauseloopimportstaproot-assets, resulting in too many symbols for the WASM build.To fix this, we will move
perms.go—which defines RPC endpoint permissions—intolooprpc. After this change, the LNC WASM client will import onlylooprpc, while the rest ofloopcan continue importingtaproot-assetswithout affecting the LNC WASM build.