Make shared threads not require any auth

[waleedkadous]

No description provided.

[abdullah-alnahas]

Thanks, Waleed, for asking me to do the review.

Seems like the "share" table is on the api_v2 branch. I suggest editing the table design as follows:

Building on Ibrahim's suggestion, I also recommend adding some metadata:

CREATE EXTENSION IF NOT EXISTS "uuid-ossp"; 
CREATE TABLE share (
    id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
    content TEXT NOT NULL,
    shared_by INTEGER NOT NULL,
    shared_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    thread_id INTEGER,
    title TEXT,
    expiration TIMESTAMP,
    FOREIGN KEY (shared_by) REFERENCES users(id),
    FOREIGN KEY (thread_id) REFERENCES threads(id)
);

What are your thoughts? @waleedkadous

[abdullah-alnahas]

After creating the share table in api_v2 and fixing the type error, everything works as expected. I ran the tests, and they all passed.

[waleedkadous]

Thanks, Waleed, for asking me to do the review.

Seems like the "share" table is on the api_v2 branch. I suggest editing the table design as follows:

Building on Ibrahim's suggestion, I also recommend adding some metadata:

CREATE EXTENSION IF NOT EXISTS "uuid-ossp"; 
CREATE TABLE share (
    id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
    content TEXT NOT NULL,
    shared_by INTEGER NOT NULL,
    shared_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    thread_id INTEGER,
    title TEXT,
    expiration TIMESTAMP,
    FOREIGN KEY (shared_by) REFERENCES users(id),
    FOREIGN KEY (thread_id) REFERENCES threads(id)
);

What are your thoughts? @waleedkadous

I think the title makes sense, but what feature do the other fields support? I am a fan of adding only what we need. We can always add these later. Let me know?