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

[W-14651333] difference in order of example payload in exchange and acm #62

Conversation

alexpmule
Copy link
Contributor

@alexpmule alexpmule commented Jan 8, 2024

Issue type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description

In ExampleGenerator component, method _jsonFromStructure

Object.keys(structure) -> return different order in salesforce and local demo. One possible solution is order array by @id prop before execute Object.keys(structure)

UI screenshots with changes

Screen.Recording.2024-01-08.at.14.56.06.mov

Checklist:

  • The branch name follows branching convention: fix/W-x/, feat/W-x/, test/W-x/* or chore/W-x/*
  • The PR title have the GUS ticket [W-xxxxx]
  • The PR is rebased with base branch
  • The PR requires a meeting with the reviewers to guide them through the changes
  • I added tests
  • I validated the fix manually
  • I have performed a self-review of my own code
  • This change requires documentation update
  • This change includes library / dependency update
  • My changes generate no new warnings

@alexpmule alexpmule self-assigned this Jan 8, 2024
@alexpmule alexpmule marked this pull request as ready for review January 8, 2024 17:58
@alexpmule alexpmule requested a review from NazaQuintero January 8, 2024 17:59
@alexpmule alexpmule merged commit 54db28c into master Jan 9, 2024
4 checks passed
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.

2 participants