feat: support custom codec files in host repositories

[ad-world]

DX-658

This ticket adds support for types packages to define schemas for their own custom codecs (that are defined with t.Type or other un-supported primitives).

To make use of this feature in the types package, first create a file titled openapi-gen.config.js. Then, add the following to the package.json in the package "customCodecFile": "openapi-gen.config.js". Then, you can populate the file with your schemas like this:

module.exports = E => {
    return { 
         CustomSchema: () => E.right({ type: 'string' })
    }
}

[ad-world]

question for reviewers: do you think the order should be switched around here? i.e. ...customCodecs comes first, so that if a downstream repo wants to redefine a schema for whatever reason, they can still do that rather than having it overwritten by the main schema definition

[ad-world]

went ahead and made the change, let me know if you think it should be reverted. I think it makes sense to give the end user more priority.

[anshchaturvedi]

I agree with this approach 👍🏽

[anshchaturvedi]

🚀

[github-actions]

🎉 This PR is included in version @api-ts/[email protected] 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version @api-ts/[email protected] 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version @api-ts/[email protected] 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version @api-ts/[email protected] 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version @api-ts/[email protected] 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀