The plugin needs a decent amount of work to be releasable to users, and there is some unknown about the ownership and prioritization of this work. I estimate there is at least a full week (or two) of focused work by a skilled Python programmer required to get this up to snuff. In particular, the following areas need improvement, or work:
The current code hard-codes a number of things instead of relying on values from the Python SDK, or from the user, like runtime choices (here and here), or target region (here for example, and everywhere a connection is established).
The current code re-establishes a connection every time an action is taken, and generally mixes in UI actions, building UI elements and manipulating UI state, with connection and query management/actions.
The plugin doesn't take any particular protections for the handling of the user's API key (probably should use a QPasswordLineEdit and ensure its value is never displayed/logged)
The loadTable feature should use temporary results storage and return the results file directly, rather than getting results back in-band and manually saving them into different format (this duplicates functionality we already have on the backend, but with more bugs)
There's a lot of code duplication in settings management, and in Spatial SQL API connection management, that needs to be refactored
After that, there's another day or two to figure out the packaging and release:
Setup CI/CD pipeline to build the Python package and plugin Zip release artifact
Update and cleanup the README, release metadata, etc.
Publish on PyPI and on the QGIS Plugin Registry
The plugin needs a decent amount of work to be releasable to users, and there is some unknown about the ownership and prioritization of this work. I estimate there is at least a full week (or two) of focused work by a skilled Python programmer required to get this up to snuff. In particular, the following areas need improvement, or work:
The current code hard-codes a number of things instead of relying on values from the Python SDK, or from the user, like runtime choices (here and here), or target region (here for example, and everywhere a connection is established).
The current code re-establishes a connection every time an action is taken, and generally mixes in UI actions, building UI elements and manipulating UI state, with connection and query management/actions.
The plugin doesn't take any particular protections for the handling of the user's API key (probably should use a QPasswordLineEdit and ensure its value is never displayed/logged)
The loadTable feature should use temporary results storage and return the results file directly, rather than getting results back in-band and manually saving them into different format (this duplicates functionality we already have on the backend, but with more bugs)
There's a lot of code duplication in settings management, and in Spatial SQL API connection management, that needs to be refactored
After that, there's another day or two to figure out the packaging and release:
Setup CI/CD pipeline to build the Python package and plugin Zip release artifact
Update and cleanup the README, release metadata, etc.
Publish on PyPI and on the QGIS Plugin Registry