Implement summarize_story for web

[AbdBarho]

Partially closes #28

There is no corresponding endpoint for submission the backend, so the submission is left unimplemented.

Merry Christmas 🎄

[fozziethebeat]

If you can, please make the two small requested changes, otherwise I'll make them in a follow up PR.

[fozziethebeat]

can you uncomment and implement the mutation code here (mostly copied from website/src/pages/grading/grade-output.tsx) with a new field in the trigger body (that i'll make work in a following PR): update_type: "text_reply_to_post"

I can make this work pretty quick.

[AbdBarho]

@fozziethebeat gladly, quick question: post in the sense of HTTP POST, or post as in reddit post?

[andreaskoepf]

post in text_reply_to_post refers to a row in the database in the post table. The post table allows to store conversation trees (threads or completions of different users or model sampling runs). The interactions like ratings and rankings are store in a separate table called post_reaction (currently users can only submit a single reaction to a given post).

[fozziethebeat]

Can you add a comment at the top here:

// TODO(#65): Unify and simplify the task paths.

[andreaskoepf]

There is no corresponding endpoint for submission the backend, so the submission is left unimplemented.

Merry X-Mas! :-) The endpoint to submit user generated summaries is the POST /api/v1/tasks/interaction endpoint, please see the text-frontend here and the discord-bot ApiClient and SummarizeStoryHandler.

[AbdBarho]

@andreaskoepf thank you, I think we already have a backend that calls the right api:

Open-Assistant/website/src/pages/api/update_task.ts

Lines 42 to 59 in 54c7a94

	const interactionRes = await fetch(`${process.env.FASTAPI_URL}/api/v1/tasks/interaction`, {
	method: "POST",
	headers: {
	"X-API-Key": process.env.FASTAPI_KEY,
	"Content-Type": "application/json",
	},
	body: JSON.stringify({
	type: "post_rating",
	user: {
	id: token.sub,
	display_name: token.name || token.email,
	auth_method: "local",
	},
	post_id: id,
	user_post_id: interaction.id,
	...content,
	}),
	});

This was a bit unclear for me at the beginning with 2 backends, it is still unclear to me why it has to be like this, but for an MVP its ok.

[yk]

thank you very much :)

just briefly regarding the "two backends". The real backend is the fastapi backend. The nextjs project is technically considered a "frontend" (even though it consists of its own back- and frontend). Other frontends exist, such as the discord bot. Frontends are responsible for making the user interaction happen and then sending all information to the backend.

The architecture is like this so we don't have to re-implement a lot of logic in all the place, like the bot, the website, etc.

[fozziethebeat]

There's a small change in the trigger body that I'll make in a follow up PR.