Skip to content

Conversation

@skyflow-vivek
Copy link
Collaborator

This PR modifies the creation of payload for detokenize method according to received feedback.

Why

  • All tokens were getting detokenized with same redaction type provided in request payload.
  • Every token should be allowed to be detokenized with its own redaction type.

Goal

  • Every token in request payload can specify its own redaction type, which is more closer to actual API design

Testing

  • The code changes were tested manually.
  • Unit tests were modified according to the new changes made.

- Update error messages and logs according to changes
- Update detokenize sample to work with new changes
@skyflow-vivek skyflow-vivek force-pushed the SK-1875-support-separate-redaction-type-for-each-token-in-detokenize-method branch from 5978ddb to fe43c66 Compare February 13, 2025 11:30
@skyflow-vivek skyflow-vivek changed the base branch from v2 to release/25.2.1 February 14, 2025 14:49
@skyflow-vivek skyflow-vivek merged commit 1284f08 into release/25.2.1 Feb 14, 2025
4 checks passed
@skyflow-shravan skyflow-shravan deleted the SK-1875-support-separate-redaction-type-for-each-token-in-detokenize-method branch June 18, 2025 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants