Add method for validate-templates endpoint

[dekatzenel]

Citrine Python PR

Description

Add method to hit backend endpoint /validate-templates

PR Type:

• Breaking change (fix or feature that would cause existing functionality to change)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Adherence to team decisions

• I have added tests for 100% coverage
• I have written Numpy-style docstrings for every method and class.
• I have communicated the downstream consequences of the PR to others.

[anduill]

this seems like a simple PR. I don't see anything glaring. This just hits the endpoint for validation right? I don't think I saw anything else.

[dekatzenel]

this seems like a simple PR. I don't see anything glaring. This just hits the endpoint for validation right? I don't think I saw anything else.

There's also a couple of small tweaks to how testing works more broadly in session.py

[anduill]

please mark this as alpha. Afterwards, I, David Garcia, will approve this Pull Request.

[dekatzenel]

please mark this as alpha. Afterwards, I, David Garcia, will approve this Pull Request.

Upon reflection, this is beta because the core backend business logic is already established and well-tested

[bfolie]

Upon reflection, this is beta because the core backend business logic is already established and well-tested

I don't think the [Beta] tag is being used in citrine-python (since it's 0.x.x, isn't everything beta?). But I agree it's not alpha, since unlike Ara we don't expect it to be volatile.

[anduill]

Ok, I approve this with the understanding that this new client feature can be expected to always work. (i.e. it's marked as BETA). Any backend services that this feature depends on are also BETA or better. If there is ANY doubt on these invariants, it might be better to mark this as ALPHA instead.