#867 ✓wontfix

An ID is required for YAML objects

Reported by Arthur | May 25th, 2011 @ 09:21 AM | in 1.3 (closed)

When you are running tests you might need to prepopulate the database with values. For this you can use YAML. This is fine, except you do need to specify an ID for each object you create. For example:

  pin:  0000
  pin:  0001
  pin:  0002

Framework version: 1.2.1
Platform you're using: Windows 7

This is correct YAML to be parsed by org.yaml.snakeyaml.Yaml

However, if you were to create this in SQL you would not need to specify the IDs for each object as they are auto generated by Play.

I propose that Play auto fills these YAML objects also. The above example could then be re-written as:

  pin:  0000
  pin:  0001
  pin:  0002

Fixtures.loadModels could then pre-parse this to auto-generate and pre-fill the missing IDs before passing to org.yaml.snakeyaml.Yaml

Comments and changes to this ticket

  • Arthur

    Arthur May 25th, 2011 @ 11:08 AM

    I should be able to write a plugin to fix this; so its probably not necessary for a change to be made to the main Play Framework.

  • Nicolas Leroux

    Nicolas Leroux October 17th, 2011 @ 09:46 PM

    • State changed from “new” to “wontfix”
    • Milestone set to 1.3
    • Assigned user set to “Nicolas Leroux”
    • Milestone order changed from “593” to “0”

    yaml files are groovy template. You can use something like that in your example:

    {list [1...50]}


    pin: {_}


    If you really need something else, I suppose you can write your own plugin/fixture class.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Referenced by