daywalker90

> 3. Make sure clnrest can handle calls to clnrest-register-path before init (save them up until after init), because this could actually happen. I don't know how to do that,...

Ok i took in all the feedback and noticed: hey! i can do that. - Everything back to 0: no more manifest stuff - new "clnrest-register-path" rpc method for clnrest...

Oh and about this: >I don't know how to do that, pretty sure this requires some changes to cln-plugin aswell? >If i could do that the "clnrest-register-path" call could take...

I've changed the behaviour of not setting the rune parameter as per the discussion in the CLN meeting. If you call `clnrest-register-path` without `rune` it now defaults to using the...

Thank you for your feedback, Shahana! > Dynamic plugin loading makes REST functionality optional, ensuring zero resource consumption for users who don’t require REST capabilities. For now, plugins that require...

It's now `clnrest-register-path path rpc_method [http_method] [rune_required] [rune_restrictions]` and i think i did everything you asked for except for the content-type stuff. > ```python > # Throws 500 Server Error...