Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IBM Waston NLU Credentials toggle not working in ClassifAI setup. #696

Closed
1 task done
iamdharmesh opened this issue Feb 6, 2024 · 0 comments · Fixed by #697
Closed
1 task done

IBM Waston NLU Credentials toggle not working in ClassifAI setup. #696

iamdharmesh opened this issue Feb 6, 2024 · 0 comments · Fixed by #697
Assignees
Milestone

Comments

@iamdharmesh
Copy link
Member

Describe the bug

The toggle for IBM Watson NLU Credentials ("Use a username/password instead?" and "Use an API Key instead?" links) to switch between username/password fields and the API key field is not functioning correctly in the ClassifAI setup. It is working fine in the ClassifAI feature setting, but it is not working properly in the ClassifAI setup.

Steps to Reproduce

  1. Go to ClassifAI setup
  2. Enable the "Classification" feature in step 1, Click "Start Setup"
  3. Navigate to Step 3 (Set up AI Providers)
  4. Select (IBM Waston NLU) as a provider
  5. Click on Use a username/password instead?/Use an API Key instead? links
  6. Notice that nothing happens on clicking the toggle link.

Screenshots, screen recording, code snippet

No response

Environment information

No response

WordPress information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@iamdharmesh iamdharmesh self-assigned this Feb 6, 2024
@iamdharmesh iamdharmesh added this to the 3.0.0 milestone Feb 6, 2024
@iamdharmesh iamdharmesh moved this from Incoming to In Progress in Open Source Practice Feb 6, 2024
@iamdharmesh iamdharmesh moved this from In Progress to In Review in Open Source Practice Feb 6, 2024
@github-project-automation github-project-automation bot moved this from In Review to Merged in Open Source Practice Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant