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

Remove links field #645

Merged
merged 1 commit into from
Nov 12, 2019
Merged

Remove links field #645

merged 1 commit into from
Nov 12, 2019

Conversation

thomasleese
Copy link
Contributor

This is one step towards solving #632 and avoids unnecessary confusion over their being two fields for accessing the links.

There are only 310 content items left which have something in the links:

irb(main):005:0> ContentItem.where(:links.nin => [{}, nil]).count
=> 310

I don't think we need to write a migration to remove this field because as new content is presented to the content store, it'll get overwritten anyway.

This is one step towards solving #632 and avoids unnecessary confusion
over their being two fields for accessing the links.

There are only 310 content items left which have something in the
`links`:

```rb
irb(main):005:0> ContentItem.where(:links.nin => [{}, nil]).count
=> 310
```

I don't think we need to write a migration to remove this field because
as new content is presented to the content store, it'll get overwritten
anyway.
Copy link
Contributor

@cbaines cbaines left a comment

Choose a reason for hiding this comment

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

Sounds good to me 👍

@thomasleese thomasleese merged commit 88614ec into master Nov 12, 2019
@thomasleese thomasleese deleted the remove-links branch November 12, 2019 10:39
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.

2 participants