Use next_node blocks in maternity-paternity-calculator #2104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@chrisroos: I'm investigating this build failure, because it looks as if it might be related to changes I've made recently. |
chrisroos
force-pushed
the
use-next-node-blocks-in-maternity-paternity-calculator
branch
from
cbde47a to
ba12229
Compare
|
I've rebased on master and force pushed. I'm expecting the build to pass. The previous failure was unrelated to these changes. |
|
Assuming the checksums are correct, this looks good to me. 👍 |
I've replaced `define_predicate` with `next_node_calculation` in an attempt to keep the code as similar as possible. I've had to update the names used by `next_node_calculation` as the question marks cause problems when the state object is converted to a hash in preparation for rendering the ERB templates.
I've replaced `define_predicate` with `next_node_calculation` in an attempt to keep the code as similar as possible. I've had to update the names used by `next_node_calculation` as the question marks cause problems when the state object is converted to a hash in preparation for rendering the ERB templates.
I've replaced `define_predicate` with `next_node_calculation` in an attempt to keep the code as similar as possible. I've had to update the names used by `next_node_calculation` as the question marks cause problems when the state object is converted to a hash in preparation for rendering the ERB templates.
chrisroos
force-pushed
the
use-next-node-blocks-in-maternity-paternity-calculator
branch
from
ba12229 to
bc998d6
Compare
|
I've rebased on master and force pushed in preparation for merging. |
chrisroos
added a commit
that referenced
this pull request
Nov 23, 2015
…ity-paternity-calculator Use next_node blocks in maternity-paternity-calculator
chrisroos
deleted the
use-next-node-blocks-in-maternity-paternity-calculator
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've agreed to consistently use
next_node {}to define our next node rules. Having a single way of defining the rules will hopefully make Smart Answers easier to develop and maintain.This will ultimately allow us to remove the predicate code (
define_predicate,on_condition,next_node_ifetc).