[AVL-3077] Cria script embedded para o form#170
Merged
Conversation
fix: corrige o caminho da API para o click_form
carlosmarquesclk
approved these changes
May 22, 2026
otanetoclk
approved these changes
May 22, 2026
elianbatistaclk
approved these changes
May 22, 2026
franciscoemanuel-clk
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumo
Este PR adiciona suporte ao Click Form Embedded na versão v3 do SDK, seguindo o padrão de embed baseado em iframe já existente no projeto.
As mudanças principais incluem:
path: /app/click_form/:keyMotivação
Habilitar integração de click-form no mesmo SDK v3 já utilizado para assinatura e verify, mantendo uma API consistente para embed no browser.
O que mudou:
Testes
Impacto / Compatibilidade
Issue tracker
Link para o card no Jira.
Code Review
Como fazer o Code Review:
CONTRIBUTING.md
Screenshots (para mudanças de UI, se houver)
[Adicione alguns screenshots das mudanças de UI inclusas no seu PR, se houver. Isso ajuda o revisor a entender como o usuário utilizaria o código do PR.]
Links e observações
[Links úteis que podem contextualizar e ajudar o revisor, por exemplo para a página de uma dependência que escolheu adicionar, ou um código que se inspirou, ou documentação externa (docs de uma API, do Vue, do Rails, etc).]
Checklist para poder mergear