snowspeeder/pi-web
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: prefer gateway plugins over remote duplicates

Browse Source
This commit is contained in:
Federico Jaramillo Martinez
2026-06-05 09:53:33 +02:00
parent b9be7de206
commit 0e64b812dd
5 changed files with 92 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plugins.html
+1
View File
@@ -302,6 +302,7 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
<ul>
<li>File and terminal helpers run against the selected remote machine.</li>
<li>Remote plugin code is loaded best-effort through the current gateway and cached for the page lifetime.</li>
<li>If the gateway already has an enabled plugin with the same original id, the gateway plugin wins and the remote duplicate stays hidden.</li>
<li>Remote theme contributions are ignored for now because themes are app-wide.</li>
<li>Mixed PI WEB versions across federated machines are best-effort and not guaranteed compatible.</li>
</ul>
docs/plugins.md
+1
View File
@@ -136,6 +136,7 @@ When machine federation is enabled, PI WEB also loads discovered plugins from th
- actions, workspace panels, and workspace labels only appear while that machine is selected;
- plugin file and terminal helpers run against that machine;
- plugin code is loaded best-effort through the current gateway and cached for the browser page lifetime;
- if the gateway already has an enabled plugin with the same original id, the gateway plugin wins and the remote duplicate stays hidden;
- remote theme contributions are ignored for now because themes are app-wide;
- mixed PI WEB versions across federated machines are best-effort and not guaranteed compatible.