Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alt ancestry column suite #659

Merged
merged 6 commits into from Mar 29, 2023

Conversation

kbrock
Copy link
Collaborator

@kbrock kbrock commented Mar 29, 2023

This is followup from #656

Running test suite with an alternate ancestry column to ensure all tests work with an alt ancestry column.

@mitsuru These tests should be more complete for you.

Things changed a bit here.
In tests, we are now always passing ancestry_column into has_ancestry (in with_model)
This value is from an env variable or defaulting to ancestry

So when code calls has_ancestry, we're not sure the name of the field in the database
so we need to be more careful.

Mostly noticeable in the tests that manually call has_ancestry
And the test of the default ancestry column name (which assumed has_ancestry was being called without values)
we are running all tests with an alt ancestry, so these are no longer necessary
@kbrock kbrock merged commit 8f06902 into stefankroes:master Mar 29, 2023
8 checks passed
@kbrock kbrock deleted the alt_ancestry_column_suite branch March 29, 2023 02:11
@mitsuru
Copy link
Contributor

mitsuru commented Mar 30, 2023

@kbrock
For me this gem is one of the indispensable ones and I am always grateful for it.

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.

None yet

2 participants