🎯 Goal

Develop a stable version of the Bitbucket connector that supports API Token authentication. This feature aims to enhance security and simplify the authentication process for users.

📋 Detailed Description

API Token Authentication

The Bitbucket connector should support API Token authentication to enhance security. Users can generate their API tokens from Bitbucket and use them to authenticate their sessions. This method is not only more secure but also reduces the hassle of managing passwords.

API Token UI for User Input

Develop a user-friendly interface where users can input their API Tokens. This UI should be intuitive, guiding users through the process of copying their API token from Bitbucket and pasting it into the connector configuration. Clear instructions and error messages should be provided to ensure a seamless experience.

🔍 Example Usage

1. User Interface:

   • Users navigate to the settings page and find the API Token input field.
   • Users enter their API Token and save the configuration.

2. Authentication:

   • The connector uses the provided API Token to authenticate requests to Bitbucket.

3. Error Handling:

   • If an error occurs, the system logs the error

Additional context

📄 Note for Contributors

Contributors are encouraged to take reference from other apps for file naming, folder structure, and coding style. Following consistent practices ensures code readability, maintainability, and a seamless development experience.

📁 File Naming and Folder Structure

• Consistency: Maintain a consistent naming convention across files and folders.
• Clarity: Choose names that clearly describe the purpose and contents of the files or folders.
• Organization: Structure folders logically to group related files together.

💻 Coding Style

• Readability: Write clean and readable code, following established coding standards.
• Documentation: Include comments and documentation where necessary to explain complex logic.
• Best Practices: Adhere to best practices in coding to ensure code quality and maintainability.

🔍 Examples

To ensure uniformity, look at examples from other well-structured apps within the project. These can provide valuable insights into effective file naming, folder structuring, and coding styles.

📢 Communication

If you have any questions or need further clarification, feel free to reach out to the team. Collaboration and open communication are key to successful project development.

Thank you for your contributions and efforts in maintaining high standards!

✨ Happy Coding! ✨

ocular-db-migration | Resolution path: db_entities
ocular-db-migration | at Object.resolve (/usr/src/app/node_modules/awilix/lib/container.js:252:23)
ocular-db-migration | at /usr/src/app/packages/ocular/dist/ocular/src/loaders/database.js:50:38
ocular-db-migration | at step (/usr/src/app/packages/ocular/dist/ocular/src/loaders/database.js:33:23)
ocular-db-migration | at Object.next (/usr/src/app/packages/ocular/dist/ocular/src/loaders/database.js:14:53)
ocular-db-migration | at /usr/src/app/packages/ocular/dist/ocular/src/loaders/database.js:8:71
ocular-db-migration | at new Promise ()
ocular-db-migration | at __awaiter (/usr/src/app/packages/ocular/dist/ocular/src/loaders/database.js:4:12)
ocular-db-migration | at /usr/src/app/packages/ocular/dist/ocular/src/loaders/database.js:43:43
ocular-db-migration | at /usr/src/app/packages/ocular/dist/ocular/src/data-source.js:77:61
ocular-db-migration | at step (/usr/src/app/packages/ocular/dist/ocular/src/data-source.js:33:23)
ocular-db-migration | npm ERR! Lifecycle script typeorm failed with error:
ocular-db-migration | npm ERR! Error: command failed
ocular-db-migration | npm ERR! in workspace: @ocular/[email protected]
ocular-db-migration | npm ERR! at location: /usr/src/app/packages/ocular
ocular-db-migration exited with code 1

Is your feature request related to a problem? Please describe.

✨ Feature Request: API Endpoint for Editing Web-Connector Indexable Links metadata

Objective:
Develop an API endpoint to enable the editing of titles and descriptions for web-connector indexable links. This will enhance the flexibility and control over the metadata associated with indexed web content.

Benefits:

• 🛠️ Enhanced Content Management: Allows users to keep their indexed data relevant and up-to-date, improving overall content quality.
• 🔄 Flexibility: Provides the ability to quickly and easily make changes to the indexed links without the need for re-indexing.

Describe the solution (or solutions) you'd like

API Endpoint Details:

• Endpoint URL: /web-connector/{link_id}
• HTTP Method: PUT
• Request Payload:

  {
    "linkId": "string",
    "title": "string",
    "description": "string"
  }
  

Describe alternatives you've considered and rejected

No response

Additional context

No response

Describe the bug

When users click on the Slack icon in the footer, instead of redirecting to the Slack page as expected, the click event redirects the user to the same page they are currently on.

URL of the page where the issue is observed.

https://www.useocular.com/

Steps To Reproduce

1. Navigate to the page containing the Slack icon in the footer.
2. Click on the Slack icon.

Expected Behavior

Clicking the Slack icon should open the Slack page in a new tab or the current window, depending on the implementation.

Screenshots/Videos

Operating System

No response

Additional context

No response

Describe the bug

Ideal Behavior

• The web-connector should schedule job only once and index docs

Bug Behavior

• Currently the web-connector scheduled job run twice to scrap data and index docs

URL of the page where the issue is observed.

http://localhost:3001/dashboard/marketplace/web-connector

Steps To Reproduce

1. Navigate to marketplace
2. Install Web-Connector App
3. Submit a link to index scrapped data from provide base_url
4. Observe the backend console to see double indexing of docs

Expected Behavior

Ideal Behavior

• The web-connector should schedule job only once and index docs

Bug Behavior

• Currently the web-connector scheduled job run twice to scrap data and index docs

Screenshots/Videos

No response

Operating System

Windows

Additional context

No response