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

Add psql dialect in editor #6065

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Add psql dialect in editor #6065

merged 1 commit into from
Jan 15, 2025

Conversation

jorg-vr
Copy link
Contributor

@jorg-vr jorg-vr commented Jan 15, 2025

This pull request adds support for the psql dialect in the editor.
As this comes on top of our genric sql support, we'll have to create a new programming language on dodona.be that uses psql or postgresql as key for the editor.

Closes #5948

@jorg-vr jorg-vr added the enhancement A change that isn't substantial enough to be called a feature label Jan 15, 2025
@jorg-vr jorg-vr self-assigned this Jan 15, 2025
@jorg-vr jorg-vr requested a review from bmesuere as a code owner January 15, 2025 14:15
Copy link
Contributor

coderabbitai bot commented Jan 15, 2025

Walkthrough

The pull request introduces PostgreSQL language support to the editor by adding a new language configuration in the additionalLanguages array. This enhancement enables PostgreSQL syntax highlighting by dynamically importing the PostgreSQL dialect from the @codemirror/lang-sql package. The change specifically defines a new LanguageDescription object with the name "postgresql", an alias "psql", and the "sql" file extension.

Changes

File Change Summary
app/assets/javascripts/editor.ts Added PostgreSQL language support with dynamic dialect loading

Assessment against linked issues

Objective Addressed Explanation
Support PostgreSQL syntax highlighting [#5948]

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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
🪧 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
app/assets/javascripts/editor.ts (1)

180-181: Consider following the naming convention.

Other language configurations in the file use uppercase for language names (e.g., "R", "Prolog", "C#"). Consider using "PostgreSQL" instead of "postgresql" for consistency.

-        name: "postgresql",
+        name: "PostgreSQL",
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 034238c and 9fd3f18.

📒 Files selected for processing (1)
  • app/assets/javascripts/editor.ts (1 hunks)
🔇 Additional comments (2)
app/assets/javascripts/editor.ts (2)

179-186: LGTM on the dialect implementation!

The implementation correctly uses the PostgreSQL dialect from @codemirror/lang-sql. This will provide proper syntax highlighting and language features specific to PostgreSQL.


179-186: Consider potential extension conflict with generic SQL.

The configuration uses the generic .sql extension which might conflict with other SQL dialects. Consider if we need to handle precedence between different SQL dialects.

Let's check if there's any existing SQL language support that might conflict:

✅ Verification successful

No SQL dialect conflicts found in the codebase.

The .sql extension is uniquely associated with the PostgreSQL configuration, and there are no other SQL dialects or conflicting language configurations present. The implementation is safe to proceed as is.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other SQL language configurations
rg -A 5 "name: .*(sql|SQL)" 

Length of output: 431


Script:

#!/bin/bash
# Search for .sql extension usage
echo "=== Searching for .sql extension usage ==="
rg -B 5 'extensions: \[.*"sql".*\]'

echo -e "\n=== Searching for language configuration array ==="
ast-grep --pattern 'const additionalLanguages = [
  $$$
]'

Length of output: 2827

Comment on lines +179 to +186
LanguageDescription.of({
name: "postgresql",
alias: ["psql"],
extensions: ["sql"],
load() {
return import("@codemirror/lang-sql").then(m => m.sql({ dialect: m.PostgreSQL }));
}
})
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Codebase verification

Add missing direct dependency to package.json

Add @codemirror/lang-sql to your package.json dependencies:

{
  "dependencies": {
    "@codemirror/lang-sql": "^6.0.0"
  }
}
🔗 Analysis chain

Verify package dependency.

Ensure that @codemirror/lang-sql is added as a dependency in the project's package.json.

Let's verify the dependency:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the package is listed in package.json
jq '.dependencies["@codemirror/lang-sql"] // .devDependencies["@codemirror/lang-sql"]' package.json

# Check if the package is imported elsewhere
rg "@codemirror/lang-sql"

Length of output: 482

@jorg-vr jorg-vr merged commit ec0232f into main Jan 15, 2025
14 of 16 checks passed
@jorg-vr jorg-vr deleted the enhance/postgresql-highlighting branch January 15, 2025 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A change that isn't substantial enough to be called a feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support PostgreSQL syntax highlighting
2 participants