Skip to content
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

Entry point assertion class for custom assertions #29

Merged
merged 1 commit into from
Jun 30, 2022

Conversation

ttddyy
Copy link
Contributor

@ttddyy ttddyy commented Jun 28, 2022

Currently, assertThat methods from custom asserts(SpanAssert,
SpansAssert, TracerAssert) do not have an entry point assertion
class. Hence, users need to static import individual assert classes.

This change introduces an entry point assertion class. Users now simply
static import this class and all assertThat methods are available for
use.

@jonatan-ivanov
Copy link
Member

@ttddyy The build is failing because of tabs vs. spaces, could you please fix it?
(The .editorconfig contains this rule so if you get your IDE to use it, it should fix it automatically.)

@jonatan-ivanov jonatan-ivanov added the enhancement New feature or request label Jun 28, 2022
@jonatan-ivanov jonatan-ivanov added this to the 1.0.0-M6 milestone Jun 28, 2022
@ttddyy
Copy link
Contributor Author

ttddyy commented Jun 28, 2022

@jonatan-ivanov ok, I have applied the rule and updated the PR.

Currently, `assertThat` methods from custom asserts(`SpanAssert`,
`SpansAssert`, `TracerAssert`) do not have an entry point assertion
class. Hence, users need to static import individual assert classes.

This change introduces an entry point assertion class. Users now simply
static import this class and all `assertThat` methods are available for
use.
@marcingrzejszczak marcingrzejszczak merged commit cfda5e9 into micrometer-metrics:main Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants