videogen schema: add support for non-string enums

[nikochiko]

Q/A checklist

• I have tested my UI changes on mobile and they look acceptable
• I have tested changes to the workflows in both the API and the UI
• I have done a code review of my changes and looked at each line of the diff + the references of each function I have changed
• My changes have not increased the import time of the server

How to check import time?

time python -c 'import server'

You can visualize this using tuna:

python3 -X importtime -c 'import server' 2> out.log && tuna out.log

To measure import time for a specific library:

$ time python -c 'import pandas'

________________________________________________________
Executed in    1.15 secs    fish           external
   usr time    2.22 secs   86.00 micros    2.22 secs
   sys time    0.72 secs  613.00 micros    0.72 secs

To reduce import times, import libraries that take a long time inside the functions that use them instead of at the top of the file:

def my_function():
    import pandas as pd
    ...

Legal Boilerplate

Look, I get it. The entity doing business as “Gooey.AI” and/or “Dara.network” was incorporated in the State of Delaware in 2020 as Dara Network Inc. and is gonna need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Dara Network Inc can use, modify, copy, and redistribute my contributions, under its choice of terms.

[coderabbitai]

📝 Walkthrough

Walkthrough

The change extends enum field handling in render_field to support string, integer, and number types beyond the previous string-only implementation. When an enum is present for any of these three types, a selectbox is rendered and the selected value is cast to the appropriate Python type using a mapping dictionary (string → str, integer → int, number → float), replacing the prior behavior that returned untyped selections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Area for attention: Verify the type casting logic correctly converts the selected value from the selectbox (typically a string) to the mapped type, and confirm the type mapping handles edge cases appropriately.

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description matches the required template structure with all sections present (Q/A checklist, import time verification details, and legal boilerplate). However, all four checklist items are left unchecked, indicating the author has not verified completion of critical quality assurance steps such as testing UI changes, verifying workflow functionality, conducting a line-by-line code review, or confirming import times have not increased. Additionally, there is no custom content describing the actual changes, rationale, or implementation details—only the boilerplate template is provided. While the structural requirements are technically met, the entirely unchecked checklist and complete absence of change-specific information makes the description incomplete and insufficient to demonstrate the PR meets the stated quality standards.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "videogen schema: add support for non-string enums" directly aligns with the primary change described in the raw summary. The change extends enum handling in render_field to support integer and number types in addition to strings, with appropriate type casting. The title is concise, clear, and specific enough that a reviewer would immediately understand the main objective of this PR without needing additional context.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch videogen-int-enum

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f6172b8 and b85c02a.

📒 Files selected for processing (1)

• recipes/VideoGenPage.py (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test (3.10.12, 1.8.3)

🔇 Additional comments (1)

recipes/VideoGenPage.py (1)

281-289: Verify None handling and enum type compatibility with gooey_gui implementation.

The concern about type casting failures is plausible. Analysis shows that value can be None if a field lacks a default (line 244: value = old_inputs.get(name) or field.get("default")). If gui.selectbox can return None, then int(None) or float(None) on line 289 will raise TypeError. While str(None) succeeds, it produces the wrong result.

However, verification requires confirming:

• Whether gooey_gui.selectbox can return None when initialized with value=None
• Whether enum fields in the schema are required to have defaults or compatible types
• Whether the framework behavior makes the suggested error handling necessary

The suggested null check and try-except handling would improve robustness, but its necessity depends on the gooey_gui implementation and schema validation guarantees.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devxpy]

i think this needs some error handling like in json below

[nikochiko]

im not clear on what would be the error case to handle.
because it's a selectbox, the value would always be one of the options. this is guaranteed by gui.selectbox even if we change some state with bad data on client side.
e.g. if int(v) fails, it would be because the schema from admin is incorrect. which i dont think we should handle here and just fail

[nikochiko]

we'll get the sentry error and then fix it from admin