When seed data is updated, Composer needs to be restarted in order to reflect that change

[michael]

I don't understand why this is. The seed is loaded here via ajax:

https://github.com/substance/tests/blob/master/test-api.js#L150

We should somehow fix this since it's gonna happen every time you write tests, and those errors are hard to spot.

You can reproduce by executing a testcase and changing the JSON in seeds/002-some-docs/local.json

[obuchtala]

I don't understand why this is. The seed is loaded here via ajax:

https://github.com/substance/tests/blob/master/test-api.js#L150

We should somehow fix this since it's gonna happen every time you write tests, and those errors are hard to spot.

You can reproduce by executing a testcase and changing the JSON in seeds/002-some-docs/local.json

Any clue?

[michael]

Really no idea. I did a hard refresh, but while all the source files are updated, the contents of the seed file seem to be cached.

[obuchtala]

Don't know if we really want to fix it.
Maybe just rely on a restart?