fix: gauzy server database migration files

[syns2191]

PR

• Have you followed the contributing guidelines?
• Have you explained what your changes do, and why they add value?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

---

Summary by CodeRabbit

• Bug Fixes
  • Corrected migration file path configuration for Electron environment to use JavaScript files instead of TypeScript files.

[coderabbitai]

Walkthrough

The pull request modifies the getMigrationsConfig function in the packages/core/src/lib/bootstrap/index.ts file. The change specifically adjusts the migration file path for Electron environments, switching from looking for TypeScript files (.ts) to JavaScript files (.js). This modification ensures proper migration file resolution in Electron contexts while maintaining the existing logic for migration configuration and validation.

Changes

File	Change Summary
packages/core/src/lib/bootstrap/index.ts	Updated migration file path for Electron environment from *.ts to *.js

Possibly related PRs

• Fix/server api not started #8645: Direct modification to migration file resolution in the same bootstrap directory
• [Fix] Table Migrations (Screening Task)  #8600: Changes to migration scripts in package.json

Suggested labels

FIX

Poem

🐰 Migrations dance, from TS to JS they leap,
Electron's path now smooth and neat
A tiny change, a rabbit's delight
Code hops forward, everything's right!
Migration magic, smooth as can be 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/core/src/lib/bootstrap/index.ts (1)

510-510: Clarify or update the comment to match the actual behavior.
The inline comment says "Only .ts if Electron," but the code clearly references *.js for Electron. Consider revising the comment to avoid confusion and to reflect that Electron uses compiled JavaScript migration files.

-? './../database/migrations/*.js'           // Only .ts if Electron
+? './../database/migrations/*.js'           // Use .js if Electron (compiled migrations)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e9b1e51 and b56f55e.

📒 Files selected for processing (1)

• packages/core/src/lib/bootstrap/index.ts (1 hunks)

[nx-cloud]

View your CI Pipeline Execution ↗ for commit b56f55e.

Command	Status	Duration	Result
nx build desktop --base-href ./	✅ Succeeded	1m 43s	View ↗
nx build desktop-api --output-path=dist/apps/de...	✅ Succeeded	27s	View ↗
nx build gauzy -c=production --prod --verbose	✅ Succeeded	5m 3s	View ↗
nx run api:desktop-api	✅ Succeeded	1m 12s	View ↗
nx run gauzy:desktop-ui --base-href ./	✅ Succeeded	3m 25s	View ↗
nx build api -c=production --prod	✅ Succeeded	1m 7s	View ↗
nx build desktop-ui-lib --configuration=develop...	✅ Succeeded	29s	View ↗
nx build desktop-ui-lib --configuration=production	✅ Succeeded	27s	View ↗
Additional runs (52)	✅ Succeeded	...	View ↗

---

☁️ Nx Cloud last updated this comment at 2024-12-30 21:25:40 UTC