feat: add API integration for uploading file

[Hitesh-Kandpal]

Portal PR Checklist

Pre-requisites

• I have gone through the Contributing guidelines for Submitting a Pull Request (PR) and ensured that this is not a duplicate PR.
• I have performed preliminary testing to ensure that any existing features are not impacted and any new features are working as expected.

PR Details

PR details have been updated as per the given format (see below)

• PR title adheres to the format specified in guidelines (e.g., feat: add admin login page)
• Description has been added
• Related changes have been added (optional)
• Screenshots have been added (optional)
• Pending actions have been added (optional)
• Any other additional notes have been added (optional)

Additional Information

• Appropriate label(s) have been added (ready for review should be added if the PR is ready to be reviewed)
• Assignee(s) and reviewer(s) have been added (optional)

---

Description:

Added API integration for uploading file

Related changes:

1. added mutation and query in grapqhl service and query file
2. created a function in file service for making API call
3. saved job id in local storage with the help of transcript.component.ts and file.service.ts
4. did the necessary changes in file-processor.component.ts to get job ids from local storage
5. add errors for transcript component in en.json file

Screenshots:

rest509.mov

Pending actions:

N/A

Additional notes:

N/A

Summary by CodeRabbit

• New Features

  • Added a file uploading functionality in the File Processor and Transcript Analyzer components.
  • Enhanced job ID management in the File Service.
  • Improved error message visibility in the Transcript Analyzer for better user guidance during file upload.

• Enhancements

  • Refined user interface by repositioning error messages next to relevant controls in the Transcript Analyzer.

• Bug Fixes

  • Corrected visual layout issues by adjusting CSS classes for file name and error messages in the Transcript Analyzer.

[coderabbitai]

Walkthrough

The recent updates focus on enhancing file processing and error handling in a web application. Modifications include the addition of job ID management in the FileProcessorComponent, improved file upload capabilities via GraphQL, and user interface adjustments in the TranscriptAnalyzerComponent to better display error messages. Additionally, new error messages have been introduced to improve user feedback during file interactions.

Changes

Files	Changes
.../file-processor.component.ts, .../file.service.ts	Enhanced job ID management and file uploading capabilities.
.../transcript-analyzer.component.html, .../transcript-analyzer.component.ts	UI adjustments and backend changes for better file handling and error display.
.../graphql.queries.ts, .../graphql.service.ts	Added new GraphQL mutation for file uploads and mutation handling method.
.../assets/i18n/en.json	Added new error messages for file selection and upload issues.

Poem

🌟 A Code Rabbit's Ode to Updates 🌟

🐇 Hop, hop, hop, in the land of code,

Where files upload and errors showed.

New paths we lay, for data's flow,

With GraphQL's charm, the bytes they go.

Cheers to changes, small and grand,

In digital fields, paw in hand. 🐾

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 22905f3 and e3a6b4c.

Files selected for processing (7)

• apps/portal/src/app/features/file-processor/file-processor.component.ts (2 hunks)
• apps/portal/src/app/features/file.service.ts (1 hunks)
• apps/portal/src/app/features/transcript-analyzer/transcript-analyzer.component.html (1 hunks)
• apps/portal/src/app/features/transcript-analyzer/transcript-analyzer.component.ts (5 hunks)
• apps/portal/src/app/graphql/graphql.queries.ts (1 hunks)
• apps/portal/src/app/graphql/graphql.service.ts (1 hunks)
• apps/portal/src/assets/i18n/en.json (1 hunks)

Files skipped from review due to trivial changes (1)

• apps/portal/src/app/features/transcript-analyzer/transcript-analyzer.component.html

Additional comments not posted (7)

apps/portal/src/assets/i18n/en.json (1)

9-11: Ensure consistency in error message keys and descriptions.

The added error messages are clear and consistent with existing keys. This should enhance user feedback during file operations.

apps/portal/src/app/graphql/graphql.queries.ts (1)

24-30: Review the GraphQL mutation for correct syntax and structure.

The mutation is well-structured and uses correct GraphQL syntax. It is designed to handle file uploads, which aligns with the PR's objectives.

apps/portal/src/app/graphql/graphql.service.ts (1)

22-34: Review the new mutate method for potential improvements in error handling and performance.

The method correctly sets up the mutation with necessary context settings for file uploads. Consider adding error handling within the method to manage GraphQL errors more effectively.

apps/portal/src/app/features/file.service.ts (2)

11-26: Review the job ID management methods for improvements in logic and error handling.

The methods for managing job IDs are implemented correctly. Consider adding error handling for scenarios where localStorage operations might fail.

---

36-40: Review the uploadFile method for correct implementation and performance.

The uploadFile method is implemented correctly and uses the GraphQL service for the mutation. Ensure that the file size and type are validated before attempting the upload to prevent unnecessary server load.

apps/portal/src/app/features/file-processor/file-processor.component.ts (1)

32-67: Review the subscription and error handling logic in the component.

The component correctly subscribes to job IDs and fetches summaries. The error handling is robust, covering network errors and API-specific errors. Consider adding more specific error messages for different types of API errors for better user understanding.

apps/portal/src/app/features/transcript-analyzer/transcript-analyzer.component.ts (1)

Line range hint 32-115: Review the file handling and error management in the component.

The component handles file selection and upload errors effectively. The use of localized error messages enhances user feedback. Ensure that file type and size validations are performed before attempting to upload to optimize performance and user experience.