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
Is your feature request related to a problem? Please describe.
Contract type regeneration is not automated, which means that developers must regenerate the type definitions individually using the pactjs-cli. For instance, if a developer creates a type, and another developer clones the repo, the latter must also retrieve the contracts and regenerate the type definitions using pactjs-cli again.
Describe the solution you'd like
To address this issue, we can automate the process entirely by maintaining a list of generated types and performing post-install actions. The list of contracts can be included in the package.json file or a custom configuration file like .kadenajs. Then, the contracts and types can be retrieved and regenerated automatically during the post-install stage by referencing this list.
Describe alternatives you've considered
An alternative could be accepting an option to specify the destination of the generated type definitions instead of the node_module folder. This would make it easier for users to share the files, as they wouldn’t have to regenerate them individually.
Note
Since implementing this feature would require a change in the workflow for generating types, it's better to schedule it for after the release of version 1.0
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Contract type regeneration is not automated, which means that developers must regenerate the type definitions individually using the pactjs-cli. For instance, if a developer creates a type, and another developer clones the repo, the latter must also retrieve the contracts and regenerate the type definitions using pactjs-cli again.
Describe the solution you'd like
To address this issue, we can automate the process entirely by maintaining a list of generated types and performing post-install actions. The list of contracts can be included in the package.json file or a custom configuration file like .kadenajs. Then, the contracts and types can be retrieved and regenerated automatically during the post-install stage by referencing this list.
Describe alternatives you've considered
An alternative could be accepting an option to specify the destination of the generated type definitions instead of the node_module folder. This would make it easier for users to share the files, as they wouldn’t have to regenerate them individually.
Note
Since implementing this feature would require a change in the workflow for generating types, it's better to schedule it for after the release of version 1.0
The text was updated successfully, but these errors were encountered: