How to use step object in Codeception v2.1 - codeception

I'm a starter to learn Codeception and I found that officical guide didn't tell me anything about the step object.
The change log of version 2.1 says
all support classes moved to tests/_support by default. Actors, Helpers, PageObjects, StepObjects, GroupObjects to follow PSR-4 naming style
So anybody can tell me how to use step object in the latest version? Or give me a simple example about that? Thanks a lot.

Here should be what you are looking for:
http://codeception.com/docs/06-ReusingTestCode#StepObjects

Related

Ktor: "io.ktor.util.pipeline.ContextDsl" in ktor 2.0

This annotation is documented here but not marked deprecated, however in the migration guide there's no mention of why it was removed, and what should be used instead.
I am totally new to Ktor, and I am supposed to port a 1.6 project to 2 while learning Ktor from scratch. Some leads in this direction will be much appreciated. Thanks
Multiple DSL markers were unified so you can use the KtorDsl annotation instead.

scoreManager.explainScore(solution) not working in Optaplanner

in the current Documentation of Optaplanner (7.40.0.Final) it says:
"The easiest way to explain the score during development is to print the return value of explainScore()"
When I create a scoreManager it doesn't have the method explainScore()
How do I get the explanation of the score in the Terminal? Where do I have to call the scoreManager?
I am working with Quarkus and my problem is very similar to the TimeTabling Problem.
Best regards and thank you in advance
Justin
Are you using the version coming with the Quarkus Platform BOM? Because in this case, it's 7.39.0.Final and that could explain your issue.
You can define the version yourself and upgrade to 7.40.0.Final. It might work, Geoffrey would be able to confirm.
He will also be able to tell you if he plans to upgrade Quarkus to 7.40.0.Final for 1.7.
That method was introduce recently. OptaPlanner 7.40.0.Final, the same version as the docs you're reading, definitely has it:
https://github.com/kiegroup/optaplanner/blob/7.40.0.Final/optaplanner-core/src/main/java/org/optaplanner/core/api/score/ScoreManager.java#L81

React Admin : How to use bootstrap instead of Material Design?

and first of all thank you for your amazing work.
The README file indicates that it is possible to use Bootstrap instead of Material Design, but I can’t find any documentation of how to implement it.
Does anybody has already done that ? Thank you in advance :)
Unfortunately, we did not find the time to document the ra-core package properly yet, so you'll have to explore the source code for now. I doubt you'll find any example for doing this as the separation into two packages (ra-core and ra-material-ui) is quite recent.
Be aware that building a bootstrap version of react-admin will take a lot of time. You'll have to explore the ra-material-ui package and build a bootstrap version of every components.

NInject 1.5 Documentation

I have a project that targets .Net Framework 3.0 - and I don't want at this stage to target it at 3.5. I do however want to use NInject in it so I'm limited to NInject 1.5 - but I'm struggling to find any documentation on how to use NInject 1.5.
I've managed to find the NInject1 wiki here but something still seems to be missing in the explanation (i.e. I can't find any Bind method as described in the Wiki).
Please anyone that could point me in the direction of some more complete documentation would be great ... if it exists
This blog post has helped no end...
I was failing to inherit from StandardModule. The original wiki didn't seem to mention this, certainly not where I was looking.

Dojo build profile.layers vs. profile.dependencies.layers?

Wow, this is totally confusing and the dojo 1.8 documentation seems a complete clusterf**k around build layers. Anybody have a clue what's going on there?
In the build script example profiles, the example amd.profile.js has profile.layers["dojo/dojo"] and the tutorial follows this same syntax.
Besides the tutorial, in the 1.8 build documentation there is no mention of this kind of structure, but of profile.dependencies.layers[n].
The documentation also references non-AMD syntax and, just to add another "layer" of confusion, there's also a profile.dependencies.layers[n].dependencies.
Which should I be using? Is this actually documented anywhere with any consistency or clarity?
I have learned that the Dojo 1.8 Reference Guide contains obsolete information regarding build profiles, but that the Dojo 1.8 Build tutorial is current:
http://dojotoolkit.org/documentation/tutorials/1.8/build/
That tutorial recommends this blog post for more information about layers and build optimization: http://www.sitepen.com/blog/2012/06/11/dgrid-and-dojo-nano-build/