Repository navigation
[ONB-4234] [Compose] Actualizar largo del nombre del titular en recipients - #63
Open
FranciscaOtero wants to merge 1 commit into
Open
FranciscaOtero wants to merge 1 commit into
FranciscaOtero wants to merge 1 commit into
Conversation
Co-authored-by: fin-compose[bot] <255610621+fin-compose[bot]@users.noreply.github.com>
Collaborator
Author
|
fin review |
FranciscaOtero
marked this pull request as ready for review
November 6, 2026 19:26
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.
Contexto
Revisé los cambios de la API pública entre el 2026-11-02 y el 2026-11-09 (se solapa con la ventana anterior, 2026-10-30 → 2026-11-06). Casi todo ya calza con la CLI. Lo único desalineado era la ayuda de
--holder-nameenv2 recipients: decía hasta 40 caracteres, pero en Chile ahora se aceptan hasta 100 (fintoc-com/pacioli#4063).Que hay de nuevo?
v2 recipients createyupdate:--holder-nameahora dice "up to 100 characters in Chile, 40 in Mexico".Tests
Consideraciones
Lo demás ya calza o quedó fuera:
POST /v1/organizationsya estaba (fintoc-com/fintoc-rails#19988, fintoc-com/fintoc-rails#20074, fintoc-com/fintoc-rails#20044).products.business_accountsentra por--products <json>./v1/organizations. DejéneedsJwsenorganizations createporque--jws-private-keyya está publicado y sacarlo rompe compatibilidad; la API ignora la firma, así que no afecta. Retirar la opción necesita soporte dedeprecatedpara opciones en el factory.PATCH /v1/organizations/{id}(fintoc-com/fintoc-rails#20103): queda fuera porque el SDK de Node (1.31.0, la última) solo tienecreatepara organizations.spliten payment intents v1/v2, invoices v2 y subscriptions v2 (fintoc-com/fintoc-rails#20108, fintoc-com/fintoc-rails#20107, fintoc-com/fintoc-rails#20011, fintoc-com/fintoc-rails#19997): es un array de objetos, así que entra por--from-jsonigual quelines. No agregué flag.split,split_appliedconredirected*,reason,payment_method_type,mx_direct_debit.error_reason) y valores nuevos de enum (inconsistent,invoice.finalization_failed) se ven engety--jsonsin cambios (fintoc-com/fintoc-rails#20380, fintoc-com/fintoc-rails#19896, fintoc-com/fintoc-rails#19906, fintoc-com/fintoc-rails#19922, fintoc-com/fintoc-rails#18922, fintoc-com/fintoc-rails#20009).--enabled-eventsytest --typeaceptan cualquier evento.tax_id.type = custom(fintoc-com/fintoc-rails#19834) y--max-completed-sessions(fintoc-com/fintoc-rails#19886) ya estaban.v2 transfers createno menciona límite, así que no cambia.