Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SD-98474 | [Madeira Madeira] Custom Identifier Improvement #1911

Merged
merged 8 commits into from
Mar 12, 2024

Conversation

emreisik95
Copy link
Contributor

@emreisik95 emreisik95 commented Mar 5, 2024

Partners can add custom identifiers to their payload. Just new field added.

Testing

We matched the custom identifiers and sent it to our side, we checked we are getting data correctly.

  • Added unit tests for new functionality
  • Tested end-to-end using the local server
  • [Segmenters] Tested in the staging environment

@joe-ayoub-segment joe-ayoub-segment self-assigned this Mar 5, 2024
@emreisik95 emreisik95 marked this pull request as ready for review March 6, 2024 17:30
@emreisik95 emreisik95 requested a review from a team as a code owner March 6, 2024 17:30
@emreisik95 emreisik95 requested a review from a team March 6, 2024 17:30
@joe-ayoub-segment
Copy link
Contributor

Hi @emreisik95 thanks for the PR. I'll schedule for review.

export const custom_identifiers: InputField = {
label: 'Custom Identifiers',
type: 'object',
description: 'You can select your custom identifiers for the event.',
Copy link
Contributor

@joe-ayoub-segment joe-ayoub-segment Mar 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @emreisik95.

2 questions:

  1. Should we default the UI to display key:value pairs?
    defaultObjectUI: 'keyvalue'

  2. Should we make the description a little more useful? Are there specific types of Custom Identifiers the user should know about? How should the user know what to place in this field? Can you provide an example or link to a doc?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it should be default key:value pairs, we are accepting it as key:value. Also, it should be undefined if partner won't use it.

For the second question, I'll align with our PM's and answer.

@joe-ayoub-segment
Copy link
Contributor

Hi @emreisik95 - I reviewed the PR. Looks good. Just one minor item pointed out. Please let me know if it's something you want to change or not?

@emreisik95
Copy link
Contributor Author

Hi @emreisik95 - I reviewed the PR. Looks good. Just one minor item pointed out. Please let me know if it's something you want to change or not?

We can keep continue like this. Thanks for your review.

@joe-ayoub-segment joe-ayoub-segment merged commit 15206a5 into segmentio:main Mar 12, 2024
9 of 10 checks passed
@joe-ayoub-segment
Copy link
Contributor

hi @emreisik95 PR deployed

@emreisik95
Copy link
Contributor Author

hi @emreisik95 PR deployed

Thanks a lot, we are checking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants