Skip to content
This repository was archived by the owner on Sep 2, 2020. It is now read-only.

Conversation

@daytonn
Copy link

@daytonn daytonn commented Apr 8, 2014

WIP getting some errors testing that I'm not sure how to address. Also cleaned up some semi-colons (I'm a lint guy).

@cmcavoy
Copy link
Contributor

cmcavoy commented Apr 8, 2014

hey @daytonn the 'types' are established, there's only four. The badgetype doesn't need to be it's own table, it can just be an enum. @christensenep has details.

@daytonn
Copy link
Author

daytonn commented Apr 8, 2014

Oh, ok, there's an interface in the issue that shows admin's having CRUD ability on types

BTW @pushcx says hi (he's pairing with me today)

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the errors you're getting during testing are actually because nothing is ever actually requiring the ./badge-type model during those tests, so the badge model gets confused because it has a relationship to a 'badgeTypes' table that never gets defined. Adding a

require('./badge-type');

line here will fix that.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yes, it had to be something stupid. I'm spoiled by rails. Make a model, voila it's available ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants