-
Notifications
You must be signed in to change notification settings - Fork 5
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
Takipi/feature/deployment routing improvement #57
Conversation
} else if (allDeps.contains(viewDepName)) { | ||
allDepViews.add(view); | ||
for (SummarizedView view : views.values()) { | ||
String deploymentNameFromView = (input.prefix != null) ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe an easier approach is to search for a deployment suffix in a "view name" and not trim the view's name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That way will match views with other prefixes.
BTW, viewName.startsWith(prefix) && viewName.endsWith(depName)
is also not accurate because there can be anything in between.
(view.name.replace(cleanPrefix(input), "")) : | ||
(view.name); | ||
|
||
for (SummarizedDeployment deployment : deployments) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should have a separate collections that after each matched deployment it will be removed from the next iteration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Removed this check, it's unnecessary.
Replaced by #58 |
Along with takipi/api-client#124