Uploaded image for project: 'Python Integrations'
  1. Python Integrations
  2. INTPYTHON-301

chatgpt-retrieval-plugin: Improve naming consistency

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: AI/ML
    • None
    • Python Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Context

      After our main pull-request was merged into openai/chatgpt-retrieval-plugin ([Feature] Addition of MongoDB Atlas datastore) jib.adegunloye@mongodb.com pointed out that the link from the README to the setup.md that goes through creation of collections and search indexes in Atlas UI was broken.

      I fixed the link, and also used the opportunity to make naming consistent.

      This pull-request does not add any new features, but it makes consistent reference to MongoDB Atlas (via "mongodb-atlas" as the DATASTORE environment variable name, and mongodb_atlas in directory names. 

      Links in documentation have been manually tested. Unit and Integration tests are passing in our Continuous Integration system.

      Definition of done

      Pull-Request is merged.

      https://github.com/openai/chatgpt-retrieval-plugin/pull/435/

       

      Pitfalls

      What should the implementer watch out for? What are the risks?

            Assignee:
            casey.clements@mongodb.com Casey Clements
            Reporter:
            casey.clements@mongodb.com Casey Clements
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: