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.
Purpose
Resolves #6. Test projects were becoming very messy due to the amount of data files required (with many having only minor differences). There was also a maintenance headache, as these data files would need to be maintained (e.g. when mandatory fields change) and this effort would be duplicated across all of the files. For example, if I had a data file named an application,json - which I wanted to make a minor adjustment to - I would need to copy everything that's in an application.json into a new file.
Approach
Add a custom build task which processes the data files in a consuming project's 'data' folder. It looks for
@extends
properties (a relative path - minus extension - to another data file) and then merges these together. In addition, folder hierarchy can now be used to construct the name passed into the data creation bindings. For example:Will allow
Given I have created 'a record with a minor difference'
. This is mostly useful when used in conjunction with@extends
.TODOs