tweak(database): make project.entity_hierarchy_id non-nullable#6649
tweak(database): make project.entity_hierarchy_id non-nullable#6649jaskfla wants to merge 3 commits into
project.entity_hierarchy_id non-nullable#6649Conversation
Summary of ChangesHello @jaskfla, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances data integrity by enforcing the non-nullable constraint for Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
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. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request makes the entity_hierarchy_id on the project table non-nullable, which is a good step for improving data integrity as it's already enforced at the application level. The changes include a database migration to apply the NOT NULL constraint and updates to the TypeScript types to reflect this change. The implementation is correct. I've added one comment regarding the process of updating generated files, suggesting to use the generator script instead of manual edits for better maintainability.
Every
projecthas one set; and we already enforce this at application level.This makes various
if (!hierarchyId) throw new Error()assertions redundant.