feat: enable multimasking function #20
Merged
Conversation
This file contains 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
gabheadz
requested changes
May 28, 2024
There was a problem hiding this comment.
Please use conventional commits https://www.conventionalcommits.org/en/v1.0.0/ to describe changes made in the commits.
JEZAPAT
changed the title
JEZAPAT
changed the title
Enhanced the data masking capability to be dynamic, allowing masking by word. Previously, the microservice only allowed masking parts of the string at the beginning, end, or middle. With this update, it is now possible to mask each word individually according to business requirements. Example of previous functionality: "Seb*** ****** *****" Example of current functionality: "Seb**** Cue*** Nav***" This was achieved by implementing logic that identifies and masks each word in the string according to the new specifications.
JEZAPAT
force-pushed
the
feature/5309738-multi-mask
branch
from
1cc36c5 to
fed5ab5
Compare
done |
gabheadz
approved these changes
May 30, 2024
|
🎉 This PR is included in version 1.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Se requiere evolucionar la capacidad de enmascaramiento de datos que hoy en día se ofrece con el objetivo de que sea dinámica.
Actualmente, solo se permite enmascarar parte del string al principio, al final o en medio, no por palabra como lo requiere el negocio.
Ejemplo de como funciona actualmente: "Seb*** ****** *****"
Ejemplo de como se espera el nuevo funcionamiento: "Seb**** Cue*** Nav***"
Se agregaron dos propiedades opcionales al enmascaramiento las cuales habilitan el enmascaramiento múltiple generando el resultado esperado, las cuales son isMultiMask y separator.
isMultiMask es una bandera con la que se habilita la funcionalidad
separator es un string con el cual se puede definir el carácter por el cual se va a separar el campo ingresado.
Al momento de dividir el campo a enmascarar por medio del separator se reutiliza la funcionalidad que existía para no afectar el comportamiento actual del código.
Se hicieron pruebas implementando la libreria en el Distribution Router.