We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
How do user provide fixtures ?
They should just implement an interface with two single methods that deal with domain objects.
setup(Vertx vertx)
tearDown(Vertx vertx)
User is responsible for creating and saving their domain objects, (since we can't do it for them, because of cascade relationships etc.)
In conf.json, the user should specify wich fixtures are run.
"fixtures" : [ "com.mycompany.fixtures.fixtures.MyUsers", "com.mycompany.fixtures.fixtures.MyAccessRoles" ]
Then in VertxMVC.bootstrap() scan for fixtures through vertx.config() and execute them.
VertxMVC.bootstrap()
The text was updated successfully, but these errors were encountered:
The fixture interface could have just 2 methods :
We have to provide a Vertx instance, so that user can access the vertx, and the eventBus eventually.
Also, keep in mind that some async stuff could be done by the end-user in fixtures, so we should return a Future.
Future
public Future<Void> startUp(Vertx vertx) public Future<Void> tearDown(Vertx vertx)
Fixtures should be loaded after vertx-mvc has been bootstrapped (obviously) but before doing anything else.
Sorry, something went wrong.
Done
aesteve
No branches or pull requests
How do user provide fixtures ?
They should just implement an interface with two single methods that deal with domain objects.
setup(Vertx vertx)
tearDown(Vertx vertx)
User is responsible for creating and saving their domain objects, (since we can't do it for them, because of cascade relationships etc.)
In conf.json, the user should specify wich fixtures are run.
Then in
VertxMVC.bootstrap()
scan for fixtures through vertx.config() and execute them.The text was updated successfully, but these errors were encountered: