Guardrails UI: Add dropdowns and modals

Open
#130 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start by locating the existing dropdown and modal implementations for the Q1 validators, then compare their customization fields with Topic relevance, Llamaguard, Profanity free, and Nsfw text. Done means each listed Q2 validator exposes its customization fields through appropriate dropdowns or modals in the guardrails UI.

Written by the indexing model from the issue text.

Description

enhancement

Describe the current behaviour?
We use drop downs and modals in the guardrails UI where it is needed to add extra customisation of the validators present, however, we currently have these drop down and modals for the Q1 validators we had on kaapi guardrails staging before 18th april which are PII remover, lexical slur match, gender assumption bias and ban words. The current guardrails UI does not support drop downs and modals for Q2 validators, making it difficult for users to customize their inputs for these validators. This limits user experience and functionality.

Describe the enhancement you'd like
Now we have many Q2 validators in staging as well such as topic relevance and all the toxicity detection validators (llamaguard, profanity free and Nsfw text), and since they are in staging , they are showing up in frontend staging as well, but the validator customization fields of all these validators are not drop downs or modals making it harder for the user to fill them if they want to, so this enhancement should be done for these validators. We should enhance the guardrails UI by adding drop downs and modals for the following Q2 validators:

  • Topic relevance
  • Llamaguard
  • Profanity free
  • Nsfw text
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
10h 40m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProjectTech4DevAI/kaapi-frontend

All issues in ProjectTech4DevAI/kaapi-frontend

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.