HCK-12369 Configure new view name compatible with the target specs: "new_view"#57
Merged
serhii-filonenko merged 1 commit intodevelopfrom Aug 21, 2025
Merged
Conversation
|
serhii-filonenko
approved these changes
Aug 21, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bug https://hackolade.atlassian.net/browse/HCK-12369 has the initial root cause: the created views contain a space in their name, "new view," which leads to undesired behavior during reverse engineering. Since this situation is not ideal, let's improve the names of the new views (as we did for other targets) to eliminate spaces.
We won't improve the reverse-engineering to deal with spaces in names as it is not a realistic use case.