Skip to content

Conversation

@Exelord
Copy link

@Exelord Exelord commented May 9, 2018

No description provided.

@Exelord Exelord merged commit f78e806 into BookingSync:fix-compound-includes May 9, 2018
],
}
includes = ['long-comments', 'long-comments.user']
includes = ['long-comments.user']
Copy link

Choose a reason for hiding this comment

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

Now you're testing only once include, not an array as before, and you did that everywhere.
From the specs it looks like you're changing functionality instead of extending, but that's not what you're doing.

Copy link
Author

Choose a reason for hiding this comment

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

Exactly. Im changing it cuz it was incorrectly implemented with the standard.
Take a look here: fotinakis#116

Right now including compound relations will also include all chain linkage.
Specs are in 100% correct :)

Copy link

@thilonel thilonel May 9, 2018

Choose a reason for hiding this comment

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

What if I do includes = ['long-comments.foo', 'long-comments.user']?
Or includes = ['upvotes', 'long-comments.user']?

Copy link

Choose a reason for hiding this comment

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

lol, all I'm saying is that the previous spec had multiple elements in the includes array and now it only has one. I see that you'd have to add new specs for that or it'd change the assert, but are you sure that those will work as intended? Wouldn't the first example I included return long-comment twice?

Copy link
Member

Choose a reason for hiding this comment

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

That's a valid concern, but I think it would be best to get back to it once we have Inbox ready, this is already merged anyway and we are running out of time really. I think there are a couple of more things to be fixed in this gem 😅

Copy link
Author

Choose a reason for hiding this comment

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

this gem is missing a lot of tests :D

Choose a reason for hiding this comment

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

yay 🙌 😅

Copy link
Author

Choose a reason for hiding this comment

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

Yes, that's not cool. but I think we will migrate from it sooner or later

Choose a reason for hiding this comment

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

One beer says it's later! 😄 It gets the job done :P

Copy link
Author

Choose a reason for hiding this comment

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

I know :D But Im not deciding when 😅

@Exelord
Copy link
Author

Exelord commented May 9, 2018

Whats the problem here? Works fine

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants