we cannot yet remove it because we still have addAssertion on Expect
and if we remove it, would also have one on AssertionContainer. Two
different definitions which would not work together. This also means:
- deprecate addAssertion/addAssertionsCreatedBy/createAndAddAssertion
in Expect, add append... to AssertionContainer
moreover:
- adjust packages.md, also remove deprecaed modules there and remove
documentation which is no longer used
- remove createRegisterJsServicesTask in build.gradle
- adjust bbc/bc due to breaking changes (removal of different types).
in the same go we have to forgive bc for infix as we no longer have
ReporterFactory and since we don't use ascii bullet points in infix
tests any more since 0.16.0 - we have established own tests for this
aspect
- rename RealTranslatorIntSpec to TranslatorIntSpec and remove the
existing TranslatorIntSpec which was intended for ReporterFactory
based implementations.
moreover:
- remove deprecated translation modules
- remove functions in api-fluent and api-infix which were only there
due to bbc, we are going to break binary compatibility anyway, so we
can remove them.
- remove Assert/AssertionPlant and co.
- remove AssertionChecker and co.
- remove deprecated verbs using still Assert
- remove ExpectImpl and co.
- remove AssertImpl and co.
- remove subject from SubjectProvider (was only there because of Assert)
- also remove PlantHasNoSubjectException and simplify corresponding
code catching it.
- remove all deprecated functionality in domain-api, domain-builders
domain-robstoll and domain-robstoll-lib which were only used by the
deprecated APIs
- remove atrium-spec, was only used by deprecated APIs
- remove spek1 dependencies, all projects are now using spek2
- move spec about disjunctive matches from domain-builders into the
corresponding APIs
introduce typealias CharSequenceOrNumberOrChar for Any
move CharSequenceOrNumberOrChar to domain-api and use in domain-impl
update setup instructions for the new infix API
include the new infix API to be published
preparation for accepting String instead of Zoned/LocalDate(Time) object
preparation for #480, #481 and #482
refer to current milestone in good_first_issue template
fix link for nullableContainer
return empty message in case callee is org.spekframework.ide
reduce code duplication also for jvm specs, add more cases to PathSpec
fix wrong replacements and workaround KT-38721 (add import next to star)
api-fluent work done
commiting requested changes
updated with comments
adding problematic classes which break the build
adding problemtic code to server to reproduce error
reproducing problematic build on CI
fix to build problem
addressing latest comment, build should pass
adjust the pseudo-keyword from exist to existing
moved infix jdk8 extension to jvm module
rebasing
so that one can easily migrate to the new infix API.
Moreover, suppress deprecations in core tests for now as we are going
to deprecate the cc-infix. We will remove this suppression once we
migrate to the new infix API
even though `expect` is not a noun and sometimes it might be confusing
it is still better than assertionContainer IMO as one quickly knows that
we talk about `Expect` and not some other potential abstract thing
For this to work we have to:
- introduce Fun0Assertions with the two assertion function
isThrowing and isNotThrowing
- rename expect which expects an act to expectOld (remove in
subsequent commit)
- fix old smoke tests which use wrong assertion verbs
