I have a request/proposal: would you consider extracting the core functionality of this plugin into a standalone Composer package (i.e. "type": "library" in composer.json), and then make the WP Plugin a wrapper around the package? My use-case is that I'm building a Composer package for WP and would like to bundle jwt-auth into it as a dependency, but because it's of type "wordpress-plugin" in composer.json, it ends up getting installed in wp-content/plugins instead of vendor, which causes problems (i.e. it's not very extendable/composable from an OSS developer POV as is -- maybe that's by design?). I would prefer not to have to fork & modify it and then maintain it myself, so just checking if you're open to this idea -- if so, I can help get the ball rolling.
I have a request/proposal: would you consider extracting the core functionality of this plugin into a standalone Composer package (i.e. "type": "library" in composer.json), and then make the WP Plugin a wrapper around the package? My use-case is that I'm building a Composer package for WP and would like to bundle jwt-auth into it as a dependency, but because it's of type "wordpress-plugin" in composer.json, it ends up getting installed in wp-content/plugins instead of vendor, which causes problems (i.e. it's not very extendable/composable from an OSS developer POV as is -- maybe that's by design?). I would prefer not to have to fork & modify it and then maintain it myself, so just checking if you're open to this idea -- if so, I can help get the ball rolling.
Let me know if you need me to elaborate :)