Skip to content
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

docs(server-commands): fix typo in command to generate migrations #9545

Merged

Conversation

nicolasrouanne
Copy link
Contributor

  • the command had --migration:generate instead of migration:generate written in the doc
  • when copy pasting it we got this error
Not enough non-option arguments: got 0, need at least 1
  • after removing the extra -- it worked as expected

- the command had `--migration:generate` instead of `migration:generate` written in the doc
- when copy pasting it we got this error
```
Not enough non-option arguments: got 0, need at least 1
```
- after removing the extra `--` it worked as expected
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

Fixed documentation typo in TypeORM migration command syntax to prevent copy-paste errors when generating new migrations.

  • Updated command in packages/twenty-website/src/content/developers/backend-development/server-commands.mdx from --migration:generate to migration:generate to match correct TypeORM CLI syntax

💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!

1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

Copy link
Member

@FelixMalfait FelixMalfait left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@FelixMalfait FelixMalfait merged commit 07fa58b into twentyhq:main Jan 10, 2025
21 checks passed
@nicolasrouanne nicolasrouanne deleted the docs/fix-typo-migration-command branch January 10, 2025 16:21
Copy link

Fails
🚫

node failed.

Log

�[31mError: �[39m SyntaxError: Unexpected token C in JSON at position 0
    at JSON.parse (<anonymous>)
�[90m    at parseJSONFromBytes (node:internal/deps/undici/undici:5584:19)�[39m
�[90m    at successSteps (node:internal/deps/undici/undici:5555:27)�[39m
�[90m    at fullyReadBody (node:internal/deps/undici/undici:1665:9)�[39m
�[90m    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)�[39m
�[90m    at async specConsumeBody (node:internal/deps/undici/undici:5564:7)�[39m
danger-results://tmp/danger-results-f3d8aa13.json

Generated by 🚫 dangerJS against ee91630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants