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

Bug/KRV-1411: tenant with same name is not working in multiarray environment #13

Merged
merged 5 commits into from
Nov 16, 2021

Conversation

karthikk92
Copy link
Collaborator

Description

Bug fix for tenant with same name is not working in multiarray environment

GitHub Issues

KRV-1411: tenant with same name is not working in multiarray environment

Checklist:

  • I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
  • I have verified that new and existing unit tests pass locally with my changes
  • I have not allowed coverage numbers to degenerate
  • I have maintained at least 90% code coverage
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • Backward compatibility is not broken

How Has This Been Tested?

myvalues :
3

tenant logs :
2

tenant added in unity array :
1

@karthikk92 karthikk92 changed the title KRV-1411: tenant with same name is not working in multiarray environment Bug/ KRV-1411: tenant with same name is not working in multiarray environment Nov 16, 2021
@karthikk92 karthikk92 changed the title Bug/ KRV-1411: tenant with same name is not working in multiarray environment Bug/KRV-1411: tenant with same name is not working in multiarray environment Nov 16, 2021
@karthikk92 karthikk92 merged commit a4fd4c0 into main Nov 16, 2021
@karthikk92 karthikk92 deleted the tenant_add_changes branch December 1, 2021 06:10
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.

3 participants