Support "$ref": "{{model:MyModel}}"

[mjmac]

Dynamically inserts references to the model.

[codecov-io]

Codecov Report

Merging #58 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #58   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           4      5    +1     
  Lines         247    276   +29     
  Branches       31     37    +6     
=====================================
+ Hits          247    276   +29

Impacted Files	Coverage Δ
src/models.spec.js	100% <100%> (ø)
src/models.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b0f280d...ee375db. Read the comment docs.

[tchock]

Awesome!

[ShaunEgan]

Any idea on when this might be released?

[tchock]

@ShaunEgan I wanted to do something for this on the weekend. There is another ticket I want to include into 1.0. But if I couldn't get to that point I would release it already.

[ShaunEgan]

Great, thanks

[ShaunEgan]

So this doesn't work when doing validation using ajv as it doesn't understand the references - do you have a suggested solution for validation with this plugin?

[mjmac]

I don't have experience with ajv, but I looked at its docs quickly. It does support $ref, which is part of the standard, but I can see why it would get confused by the unprocessed references.

I can't really think of a great solution. We could change this feature so that instead of $ref we use a different keyword ('awsref'?), and then at least things which are expecting a real reference won't get confused. But I don't think that really solves your problem, which is that you want to do validation using composition of the unprocessed model definitions. I think you're going to have to pick one way of doing it or the other. I am holding out hope that AWS adds support for enabling validation via CloudFormation soon.

[vmtzkr]

Could you please publish a new version on npm?

[tchock]

Yes, will do this today

[tchock]

@vilius-rugaitis Released with version 1.0 :)

[vmtzkr]

Somehow, I cannot update the package over npm. Or does npm have some kind of update review processes?

[tchock]

@vilius-rugaitis Oh, my bad. thought this package had an automated publishing process in travis ci.
Have published it manually now :)