feat(websites): export domain and SSL status enums - #120
Merged
Conversation
Kody Review CompleteGreat news! 🎉 Keep up the excellent work! 🚀 Kody Guide: Usage and ConfigurationInteracting with Kody
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
pcfreak30
marked this pull request as ready for review
September 4, 2026 13:19
Code Coverage ReportTotal Coverage: 13.5% Generated from commit: a5b28bb |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exposes
DomainResponseStatusandSSLStatusas SDK type aliases withconstants for each generated enum value, matching the existing
GatewayNamespaceexport pattern.This pull request exposes the domain and SSL status enums from the underlying API client as part of the SDK’s public API. It adds type aliases (
DomainResponseStatusandSSLStatus) and named constants for all possible values, along with documentation comments. This allows consumers to reference these statuses directly, improving code clarity and type safety when working with domain bindings and certificate states.