-
Notifications
You must be signed in to change notification settings - Fork 321
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
4065: Chainsaw for Funcs Part 1 - Func Authoring Parity with New Routes r=vbustamante a=britmyerss **Changes in this PR** **New front end objects for Function Authoring** - `FuncSummary` includes details about the function, the `func_id`, `FuncKind`, `display_name`, `name`, all function arguments, and all bindings for that Function - `FuncBinding` - is the evolution of `FuncAssociations` and represents the intersection of the Func metadata and all of the required information for that Function to be configured and used by a Schema Variant (or Component) - `FuncCode` is the actual code body and all the correct type information for type checking when authoring **New Routes for Function Authoring** All routes for func authoring follow the same pattern of `api/v2/workspaces/{workspace_id}/change-sets/{change_set_id}/funcs` Reorganized the payloads for the routes to deduplicate how the front end is getting data, following the pattern we adopted for Func Arguments and Attribute Bindings Abolished the `save_func` hammer and created separate CRUD routes for creating, modifying and deleting FuncBindings for Auth, Qualifications, Actions, and Code Gen Funcs. **`FuncBindings` in the Dal** This enum encapsulates the logic for creating, updating, and deleting the various prototypes and related configuration metadata for how functions relate to Schema Variants/Components. I duplicated the existing tests to exercise the new code, but this is an area that we will definitely expand integration tests as the immutability for schema variants and functions come into play. This is set up to support the ability to add bindings for intrinsics (including setting default values) via the UI, but that work will be a follow on. ** New WS Events** This is still very WIP as I work with `@jobelenus` on the necessary shape for these For now, I've left all of the existing code/routes in tact so this is effectively toggled, but once the front end consumes these new routes I'll be able to remove what's been duplicated. Huge shoutout to `@nickgerace` for the work on porting authoring to the new engine - I was able to largely use the existing FuncAuthoringClient for the function specific authoring work! <div><img src="https://media4.giphy.com/media/eMRmnt6MIhfcJsMexH/200.gif?cid=5a38a5a2369ozkmc3tb3tljaj85un52xuzs846z80bww1jis&ep=v1_gifs_search&rid=200.gif&ct=g" style="border:0;height:168px;width:300px"/><br/>via <a href="https://giphy.com/family-guy/">Family Guy</a> on <a href="https://giphy.com/gifs/family-guy-family-guy-peter-chainsaw-eMRmnt6MIhfcJsMexH">GIPHY</a></div> Co-authored-by: Brit Myers <[email protected]>
- Loading branch information
Showing
59 changed files
with
5,455 additions
and
210 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.