Remove axios dependencies from ALIA UI

[TamiTakamiya]

Jira Issue: https://issues.redhat.com/browse/AAP-60189

Assisted-by: Claude Code
Generated by: Claude Code

Description

Testing

Steps to test

1. Pull down the PR
2. ...
3. ...

Type of Change

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to break)
• Security fix
• Performance improvement
• Code refactoring
• Documentation update
• CI/CD update

Backport Policy

This change should be:

• Not backported - main/master only
• Backported to specific releases (add labels after merge)

Automated Backport Instructions

After this PR is merged, add one or more labels to automatically create backport PRs:

• backport/stable-2.4 - Backport to stable-2.4 branch
• backport/stable-2.5 - Backport to stable-2.5 branch
• backport/stable-2.6 - Backport to stable-2.6 branch
• backport/all - Backport to all active stable branches
• no-backport - Explicitly mark as not needing backport

Backport Justification

Special backport considerations:

Scenarios tested

Production deployment

• This code change is ready for production on its own
• This code change requires the following considerations before going to production:

---

Note

Medium Risk
Moderate risk because it changes core network/request behavior (timeouts, error detection, request payload formatting) and could subtly affect production API interactions despite tests being updated.

Overview
Replaces axios with the native fetch API across both chatbot UIs, updating the chat request, feedback submission, and health-check calls (including adding an AbortController-based timeout for non-streaming chat and mapping timeout/429 error handling to fetch semantics).

Removes the axios dependency from both package.json/lockfiles, updates unit tests to mock global.fetch instead of axios (including a new stringified-body matcher), and adds a small guard in ReferencedDocuments to safely handle non-array referenced_documents.

^{Written by Cursor Bugbot for commit b762993. This will update automatically on new commits. Configure here.}

[github-actions]

# npm audit report

lodash  4.0.0 - 4.17.21
Severity: moderate
Lodash has Prototype Pollution Vulnerability in `_.unset` and `_.omit` functions - https://github.com/advisories/GHSA-xxjr-mmjv-4gpg
fix available via `npm audit fix`
node_modules/lodash

1 moderate severity vulnerability

To address all issues, run:
  npm audit fix

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

[cursor]

GET mock logic duplicated within mockFetchPost function

Low Severity

The mockFetchPost function duplicates the entire GET request handling logic from mockFetchGet (lines 13-25 in mockFetchGet are copied to lines 33-46 in mockFetchPost). This internal redundancy within the same file means changes to GET mock behavior require updates in two places, increasing risk of inconsistency.

Additional Locations (1)

• ansible_ai_connect_chatbot/src/AnsibleChatbot/AnsibleChatbot.test.tsx#L34-L48

 

[cursor]

Duplicated custom vitest matcher across test files

Low Severity

The objectStringContaining custom vitest matcher is identically duplicated in both aap_chatbot/src/App.test.tsx and ansible_ai_connect_chatbot/src/App.test.tsx. This matcher could be extracted to a shared test utilities file to reduce maintenance burden and ensure consistent behavior across both packages.

Additional Locations (1)

• ansible_ai_connect_chatbot/src/App.test.tsx#L30-L44

 

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud