Dev minor

[emrgnt-cmplxty]

Important

This PR renames POSTGRES_PROJECT_NAME to R2R_PROJECT_NAME, updates knowledge graph creation with cost estimation, and modifies API endpoints and documentation accordingly.

• Environment Variables:
  • Rename POSTGRES_PROJECT_NAME to R2R_PROJECT_NAME in .env.example, integration-test-workflow-debian.yml, py-ci-cd.yml, r2r-js-sdk-integration-tests.yml, and other files.
• Knowledge Graph:
  • Update create-graph and enrich-graph commands in graphrag.mdx to include cost estimation steps.
  • Add run and estimate options to create_graph and enrich_graph in kg.py.
  • Implement get_creation_estimate and get_enrichment_estimate in kg_service.py and postgres.py.
• API Changes:
  • Update put_user_app in auth_router.py to allow superuser status updates.
  • Add get_entities and get_triples endpoints in kg_router.py.
• Testing and SDK:
  • Update r2rClientIntegrationUser.test.ts to include tests for user profile updates and login.
  • Modify updateUser function in r2rClient.ts to include userId and isSuperuser parameters.
• Documentation:
  • Update whats-new.mdx to reflect changes in version 0.3.20.
  • Modify postgres.mdx, database.mdx, and vector_store_issues.mdx to reflect environment variable changes.

^{This description was created by for 989ce1a. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 989ce1a in 2 minutes and 4 seconds

More details

• Looked at 4234 lines of code in 76 files
• Skipped 2 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. templates/agentic_rag_chatbot/web-app/public/data/r2r-installation.html:72

• Draft comment:
  Update POSTGRES_VECS_COLLECTION to R2R_PROJECT_NAME for consistency with other changes.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  The comment is suggesting a change for consistency, which is a valid code quality improvement. The diff shows that R2R_PROJECT_NAME is introduced, which aligns with the comment's suggestion. This indicates that the comment is relevant to the changes made in the diff.
  I might be missing whether the change is actually necessary for functionality or if it's purely for naming consistency. The comment doesn't specify if there's a functional impact.
  Even if the change is for naming consistency, it can still be important for code readability and maintainability, which are valid reasons to keep the comment.
  The comment is relevant to the changes made in the diff and suggests a valid improvement for consistency. It should be kept.

2. templates/ycombinator_graphrag/web-app/public/data/r2r-installation.html:72

• Draft comment:
  Update POSTGRES_VECS_COLLECTION to R2R_PROJECT_NAME for consistency with other changes.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_80I8UyAPlquId28g

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.