You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a toolkit midway through the development of an existing codebase, is it possible to use the existing code templates (of a toolkit) to identify existing code (in the codebase) that matches the code template [close enough] to derive new solution items with suggested configuration?
Here is the use case:
I build a new toolkit that helps build new Rest APIs in a particular codebase. The toolkit was [of course] based off of code templates that were extracted from that codebase to start with, with some configuration attributes to represent the variability of any API.
These code templates were then programmed (substitutions) with values from some pattern meta-model.
Now, after building the toolkit, and defining the code templates for that toolkit to realise new code in this codebase. I would then use to the toolkit to add/generate more APIs in that codebase. But that codebase (at this point in time) will no doubt have API's that were not generated by the toolkit.
Is it possible to find existing code (in that codebase) that matches (near enough - account for variance in human error) to a degree that allows the toolkit to reverse engineer or guess new solution configuration to represent the existing API's in the codebase? so that the user of the toolkit does not have to go back into the toolkit solution and add the configuration manually to represent the existing API's?
Perhaps to toolkit can do the majority of the heavy lifting, leaving the user of the toolkit to fill in some blanks of missing configuration (that could not be derived)?
The text was updated successfully, but these errors were encountered:
When using a toolkit midway through the development of an existing codebase, is it possible to use the existing code templates (of a toolkit) to identify existing code (in the codebase) that matches the code template [close enough] to derive new solution items with suggested configuration?
Here is the use case:
I build a new toolkit that helps build new Rest APIs in a particular codebase. The toolkit was [of course] based off of code templates that were extracted from that codebase to start with, with some configuration attributes to represent the variability of any API.
These code templates were then programmed (substitutions) with values from some pattern meta-model.
Now, after building the toolkit, and defining the code templates for that toolkit to realise new code in this codebase. I would then use to the toolkit to add/generate more APIs in that codebase. But that codebase (at this point in time) will no doubt have API's that were not generated by the toolkit.
Is it possible to find existing code (in that codebase) that matches (near enough - account for variance in human error) to a degree that allows the toolkit to reverse engineer or guess new solution configuration to represent the existing API's in the codebase? so that the user of the toolkit does not have to go back into the toolkit solution and add the configuration manually to represent the existing API's?
Perhaps to toolkit can do the majority of the heavy lifting, leaving the user of the toolkit to fill in some blanks of missing configuration (that could not be derived)?
The text was updated successfully, but these errors were encountered: