ふたつ目以降のカテゴリが作成できない about lokka

[tomykaira]

slug を入力しないカテゴリを複数作成できないです。

[tomykaira]

パッチを作成しました。
テストしてみてください： https://github.com/komagata/lokka/pull/142

The cause was that the POSTed slug is "" when no slug is specified.
Category model had unique constraint for slug and title, therefore @category.save failed.

In Entry model, uniqueness is ensured with dm-validations, and it does not use DB constraint.
I follow the way.

[komagata]

Looks like CI failed.

http://travis-ci.org/#!/komagata/lokka/jobs/596760

[tomykaira]

CI still fails against Postgres.

http://travis-ci.org/#!/komagata/lokka/builds/613447

That is because spec_seeds.rb specifies :id of Category's first instance apparently,

Category.create(:id => 1,
                :title => 'Test Category',
                :created_at => created_at,
                :updated_at => updated_at)

but my category_spec.rb does not.

The main cause is that datamapper does not update categories_id_seq when :id is specified.
(Simple test: https://gist.github.com/1726651)

I did not specify :id because it is not specified when created in application.
Therefore, I'm not happy with the idea that create all Category items with :id in that unit test.
However, I know that controlling :id is important for integration tests. So it could be the only possible solution.

By the way, I disagree with using the same fixture between all test, because it makes implicit dependency between tests like this.

How can we work around this problem? Tell me your idea!

[komagata]

Oh I see.
I think so too. I don't want to use :id and fixture.
It's no probrem that fixture will replace with "fixture replacement library".

[tomykaira]

Now CI passes.
@johnny-miyake , thank you for reporting problem.
@komagata , thank you for kind advice.

[komagata]

omg! CI is back! thanks @tomykaira