feat(data_modeling): add 'record' value to Container 'used_for' field#2391
feat(data_modeling): add 'record' value to Container 'used_for' field#2391evertoncolling wants to merge 1 commit intomasterfrom
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2391 +/- ##
==========================================
- Coverage 90.96% 90.95% -0.01%
==========================================
Files 192 192
Lines 26142 26142
==========================================
- Hits 23779 23777 -2
- Misses 2363 2365 +2
🚀 New features to boost your workflow:
|
Description
Add support for the 'record' value in the
used_forfield for bothContainerandContainerApplyclasses in the data modeling API.Existing tests already provide adequate coverage for this change, as no tests explicitly validate the list of allowed
used_forvalues and the new value is additive and doesn't break existing functionality.Checklist:
If a new method has been added it should be referenced in cognite.rst in order to generate docs based on its docstring.