Rename Testcontainers for C to Testcontainers Native#47
Conversation
This renames every instance of "Testcontainers for C", "Testcontainers C", and "testcontainers-c".
|
@seffradev, should we rename all the instances? Or should we keep the naming for distributables, e.g.?
|
|
It is a fair question, and I will elaborate (and possibly change this PR) when I've had time to write a thorough proposal for a design that addresses your concerns on the C API design. In short, I'm thinking:
The proposal will also mention ideas for how the modules (currently WireMock) would be set up and designed around this. |
|
@seffradev fine be me, and thanks. I think we are on the same page. |
|
I'm closing this in favor of #53. |
|
OK, I think we agree in principle. I will suggest a patch with naming conventions to CONTRIBUTING, and then we can align the naming |
1 similar comment
|
OK, I think we agree in principle. I will suggest a patch with naming conventions to CONTRIBUTING, and then we can align the naming |
What does this PR do?
This renames every instance of "Testcontainers for C", "Testcontainers C", and "testcontainers-c".
Why is it important?
It makes the naming consistent throughout the project. I am expecting a minimal breakage due to renamed headers and project, but should be a quick fix.
Related issues