-
Notifications
You must be signed in to change notification settings - Fork 29
Generate gafferpy core api using fishbowl #981
Comments
As part of this, fishbowl should be generally cleaned and moved under gafferpy as a tool. It will only be responsible for generating implementations for Gaffer's Operations, Functions, Predicates and Binary Operators. |
As well as this it can now generate the GET endpoints in gaffer_config.py |
This issue has been re-scoped to just cover the clean up and movement of fishbowl into gafferpy as a sub-module. |
The part of this issue that related to automating the usage of fishbowl to maintain gafferpy has been moved into a separate issue, as the work is blocked. |
* gh-981: Cleanup gafferpy * gh-981: Format readme * Revert "gh-981: Format readme" This reverts commit 3e8c48c. * gh-981: Rework how different client libraries are used * gh-981: Tidy up warning * gh-981: Fix tests * gh-981: Moved fishbowl under gafferpy, works with the gafferpy connector * gh-981: Make json return optional * gh-981: Operations are generated and tested * gh-981: Binary operators added * Added generated functions * Add generated predicates * Fishbowl will make required args actually required * Fix GetElements Op with helper * Disable test when not using spring-rest api * Generate config paths * Cleanup paths and modules * Bugfix config and cleanup * Add licenses to fishbowl and add generated notice * Change fishbowl README * Cleanup README * Backwards compatibility for imports * Cleanup docstrings * Refactor to use **kwargs * Use core-rest endpoint so tests can pass * Fixed bug with If operation extension * Added comments where generated code imported * Remove SeedMatching * Update READMEs * Fixed whitespace * Added temp fix for missing function endpoints * Added to init.py and corrected uri * Added some doc about spring-rest /version * Added https test
Closed by #1015 |
Currently, new Operations in Gaffer require a manual and tedious update to the gafferpy api (e.g. 2e8afc1).
Instead, this code could be generated automatically using fishbowl.
Rather than a developer having to do this manually, it would be nice if there was some way to automate gafferpy code changes when the Gaffer version gets updated in a release.
This would effectively mean the core part of gafferpy would be manually maintained but all the Operations etc. that can be generated will be automatically updated/maintained.
The text was updated successfully, but these errors were encountered: