MINIFICPP-910 - Extend StringUtils with string join capability#585
MINIFICPP-910 - Extend StringUtils with string join capability#585arpadboda wants to merge 1 commit intoapache:masterfrom
Conversation
libminifi/src/utils/StringUtils.cpp
Outdated
| @@ -0,0 +1,162 @@ | |||
| /** | |||
There was a problem hiding this comment.
The content of this file is mostly moved from the header, the changes I made were to make linter happy. Some of these functions still leave space for improvement.
bdb1331 to
495bb52
Compare
There was a problem hiding this comment.
Thanks @arpadboda I'll launch this on some devices and merge if good.
As a project we generally don't commit dead production code -- but I can understand the desire to close this one out so I'll merge if it passes those tests. Thanks!
I think it's totally fair to leverage a need for code like this on others' pull requests as it begins a chain of testability.
btw, I don't suspect the builds to fail with this, but I perform these builds on anything in libminifi -- so I'll merge it when that is successfully complete, hoping in the next few hours. Thanks again!
|
@phrocker : thanks, usage will come soon! :) |
|
@arpadboda I hope to get this merged tomorrow. One of the builds passed, but the other devices are working on higher priority PRs. raspberry pi 3 actually passes now on all variants of the OS so I think that one is good. Thanks! I'll check the other devices once those other PRs are finished building. |
phrocker
left a comment
There was a problem hiding this comment.
just have one more platform to succeed. if it does I'll merge this. Thanks!
This closes apache#585. Signed-off-by: Marc Parisi <phrocker@apache.org>
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically master)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.