Skip to main content

[Issue 113] New - Public constants in test export sources must have proper names

1 reply [Last post]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Dmitri Trounine

And what if we move all test export related classes in one package like
I tried it and it works.

> But first, we need to make sure we even WANT these things to be exposed as
> public constants. See also ISSUE #105: Too many exposed API in new code.
> Just think of it. Any change in our test export implementation could render some
> of these constants obsolete, but we will never be able to remove them (or
> change, for that matter) in order not to break the compatibility.
> P2 for this issue to make sure we address it in FW 1.2 when the API is new and hot.

To unsubscribe, e-mail:
For additional commands, e-mail: