Make new talk_links kinda work with web1

Description

The old website expects a slides_link field in the talks table. We now store this information in the new talk_links table, but we need to manage the migration here.

When a talk_link is created, add the URL to the talks table if there is not already a URL there.

When a talk_link is edited and the URL changes, check if the same URL was stored in the talk.slides_link column and if so, update that also.

When a talk_link is deleted, if its URL is used in the talks table, empty that field. If there are other valid talk_links for this talk, add one to the talks table.

Activity

Show:

Scott Dutton December 7, 2016 at 8:24 PM

Are these being worked on or free to pick up ?

Luciano Queiroz October 28, 2016 at 3:19 PM
Edited

I'd suggest we have a primary link of slides type, so we can keep track of it more easily and manage the legacy talks.slides_link column. But the way you put it above sounds good!

Andreas Heigl October 28, 2016 at 3:18 PM

That's not a problem. When someone adds some links but no "slide" link there is no slides-link set in the talks-table. The first link that is added to a talk that is marked as "slide"-link will be synched over to the talks table and that's where legacy is getting it's information from.

So as long as there is no slides link legacy will show no link at all.

Luciano Queiroz October 28, 2016 at 3:04 PM

So we have multiple type of links, if the user first adds a type that isn't "slides" the legacy site expects that the link is a slides type... We need to think about other approach

Luciano Queiroz October 28, 2016 at 2:53 PM

Moving the conversation from https://github.com/joindin/joindin-api/pull/265 to here.

Details

Assignee

Reporter

Components

Priority

Created November 16, 2015 at 3:22 PM
Updated December 7, 2016 at 8:24 PM