dni ⚡
dni ⚡
bump! like that PR, a couple of tests would be very nice for this!
this was fixed by: https://github.com/lnbits/lnbits/pull/2340
ha :) it was a reminder for me and @arcbtc but i dont quite remember aswell? i think this can be closed? wwwhat do you think ben?
fixed in latrest withdraw extension
true, lnurl does not handle it. Here you see in the code we only check LNURL in the beginning to decode its, no lud1 fallback at all. https://github.com/lnbits/lnbits/blob/main/lnbits/core/views/api.py#L600 it is...
hm, that previous message was kinda weird... is this issue resolved yet? i see its been a year since you reported it, we are now at `0.12.8`
we need a string like this `LNBITS_EXTENSIONS_DEFAULT_INSTALL="jitsi,copilot,gerty,jukebox,lnticket,tpos,usermanager,example,events,lnurldevice,smtp,discordbot,hivemind,boltcards,nostrnip5,splitpayments,boltz,satsdice,offlineshop,subdomains,streamalerts,livestream,lnurlp,deezy,invoices,withdraw,paywall,market,satspay,bleskomat,tipjar,lndhub,scrub,lnaddress,watchonly"` and export that
https://github.com/lnbits/lnbits-extensions/blob/main/util.sh#L32 ``` # gives you lnbits env variables for all extensions env() { env=$(jq -rj '[.extensions[].id] | unique | .[]+","' ./extensions.json | sed 's/.$//') echo "LNBITS_EXTENSIONS_DEFAULT_INSTALL=\"$env\"" } ```
but i still think this CI pipeline should be triggered and ran in `lnbits-extensions` repository, when an extensions is updated! maybe i am wrong and maybe both is useful
i like the idea with the user manager! @jackstar12