acl-services / acl-services/paprika

Async action in confirmation Component not showing pending state correctly

Aberta
#342 0 comentários 0 reações 1 responsável Reivindicada por @tristanjasper Ver no GitHub
Medium Priority →
Linguagem predominante
JavaScript
Estrelas
54
Forks
10
Merge médio
1d 12h
PRs com merge (30d)
6

Descrição

# Bug Report

Added story to demonstrate isPending state
Ensure onClose callback is closed after the confirmation has animated closed.
Ensured that the isPending button state doesn't cause wrapping issues in the Confirmation content area.

## Prerequisites
**This is just a checklist, please delete this section after**
Please answer the following questions for yourself before submitting a bug report.
- [x] I checked to make sure that this bug has not already been filed
- [x] I reproduced the bug in the latest version of paprika
- [ ] Please label as, low / medium / high priority

*Please fill in as much detail as possible below*

## Expected behavior
*Please describe the behavior you are expecting to happen.*

## Current behavior
*What is the current behavior?*

## Screenshots / Gifs / Codepens
*Include media to help illustrate the bug. Gifs help a lot!*

## Additional context
*Please provide any more additional details to illustrate the bug*

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Direção de pesquisa

Start by finding the Confirmation component and any Storybook story for isPending, since the report mentions a pending-state story. Locate where onClose is currently fired and check whether it runs after the close animation; adjust flow so it is delayed until completion. Inspect the Confirmation content area/button rendering path for pending-state wrapping behavior. Validate by running the relevant Confirmation component/story checks and confirming pending visuals and close timing are correct.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
javascript, react
Domínio
frontend
Tipo de issue
Bug
Dificuldade
2/5
Tempo estimado
1-3 horas
Status de atividade
Estagnada
Clareza
Razoavelmente clara
Facilidade para iniciantes
30/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.