-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds Missing ExpirationDate Field on Key Object #320
Conversation
WalkthroughThe recent update introduces a new Changes
Possibly related issues
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- Deepgram/Models/Manage/v1/Key.cs (1 hunks)
Additional comments not posted (1)
Deepgram/Models/Manage/v1/Key.cs (1)
51-56
: LGTM! Verify JSON serialization attributes.The
ExpirationDate
property is well-documented and follows the existing pattern. Ensure that theJsonIgnore
andJsonPropertyName
attributes are correctly applied.Verification successful
Verified! The JSON serialization attributes for the
ExpirationDate
property are correctly applied.The
ExpirationDate
property inDeepgram/Models/Manage/v1/Key.cs
has the appropriateJsonIgnore
andJsonPropertyName
attributes, ensuring correct JSON serialization behavior.
JsonIgnore(Condition = JsonIgnoreCondition.WhenWritingNull)
JsonPropertyName("expiration_date")
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the JSON serialization attributes of the ExpirationDate property. # Test: Search for the ExpirationDate property and check its attributes. rg --type cs -A 5 $'public DateTime? ExpirationDate { get; set; }'Length of output: 229
Script:
#!/bin/bash # Description: Verify the JSON serialization attributes of the ExpirationDate property. # Test: Search for the ExpirationDate property and check its attributes. rg --type cs -A 5 $'public DateTime\\? ExpirationDate { get; set; }'Length of output: 232
Script:
#!/bin/bash # Description: Verify the JSON serialization attributes of the ExpirationDate property. # Test: Search for the ExpirationDate property and check its attributes. rg --type cs -A 5 'public DateTime? ExpirationDate { get; set; }'Length of output: 229
Script:
#!/bin/bash # Description: Verify the JSON serialization attributes of the ExpirationDate property. # Test: Search for the ExpirationDate property and check its attributes. grep -F -A 5 'public DateTime? ExpirationDate { get; set; }' $(find . -name '*.cs')Length of output: 14532
Proposed changes
Addresses issue: #319
Types of changes
What types of changes does your code introduce to the community .NET SDK?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
NA
Summary by CodeRabbit
New Features
ExpirationDate
property for API keys, allowing better management of key lifecycle.Documentation
ExpirationDate
property.