Skip to content

feat: add q&a conversations #1576

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

Merged
merged 33 commits into from
Apr 7, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
33 commits
Select commit Hold shift + click to select a range
9730d5d
Merge pull request #601 from mfts/feat/pptx
mfts Sep 16, 2024
e766e5e
Merge branch 'main' into staging
mfts Sep 21, 2024
ce9050c
Merge branch 'main' into staging
mfts Mar 6, 2025
b7ad270
[staging] Merge pull request #1540 from mfts/feat/new-click-tracking
mfts Mar 6, 2025
17dcb1b
Merge pull request #1544 from mfts/fix/middelware
mfts Mar 7, 2025
33b3991
Merge branch 'main' into staging
mfts Mar 9, 2025
6181dea
feat: add second cookie after signin
mfts Mar 9, 2025
2fd50cf
fix
mfts Mar 9, 2025
efd2960
chore: cursor rules
mfts Mar 16, 2025
d848e55
refactor: change db table conversation to chat
mfts Mar 16, 2025
390d76d
refactor: make subpage navbar better for datarooms
mfts Mar 16, 2025
950e9d0
Merge branch 'main' into feat/qna
mfts Mar 16, 2025
d134d5a
refactor: change name
mfts Mar 17, 2025
3ae2b64
Merge branch 'main' into feat/qna
mfts Mar 26, 2025
3f10fb4
Merge branch 'main' into feat/qna
mfts Mar 29, 2025
1a1bee1
Merge branch 'main' into feat/qna
mfts Apr 2, 2025
ac04841
feat: add conversations (q&a)
mfts Apr 4, 2025
4fec2a6
feat: add maxPages as an configable option
mfts Apr 4, 2025
558480a
refactor: cleanup nav props
mfts Apr 4, 2025
92b4d5c
feat: update view api routes
mfts Apr 4, 2025
60ecc05
chore: cleanup
mfts Apr 4, 2025
4daa628
feat: add replyTo in resend email
mfts Apr 4, 2025
ba5741b
chore: cleanup unused code
mfts Apr 4, 2025
c1a2ece
refactor: viewer components
mfts Apr 4, 2025
95eab7f
Merge branch 'main' into staging
mfts Apr 4, 2025
37630cd
Merge pull request #1573 from mfts/feat/qna
mfts Apr 4, 2025
e2cadd7
feat: toggle dependency link settings for conversations
mfts Apr 5, 2025
69097e4
chore: add proper error message
mfts Apr 5, 2025
16bad2a
fix: add proper error message
mfts Apr 5, 2025
c819e7d
Merge branch 'main' into feat/qna
mfts Apr 7, 2025
25623f9
fix
mfts Apr 7, 2025
79b040a
fix: enable convo limits
mfts Apr 7, 2025
9b7423f
fix: allow trial
mfts Apr 7, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions .cursor/rules/rule-claude-sonnet-37.mdc
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
description:
globs:
alwaysApply: true
---
---
description: Base Guidelines for Sonnet-3.7 + Cursor Agent
globs: *,**/*
---

# Instructions

1. Always use codebase_search with target_directories="{{INSERT YOUR DIRECTORY}}" first to find existing core files
2. Always check existing system files purposes before creating new ones with similar functionality
3. Always list the cursor rules youre using

# Optional

- If a prompt or request specifies certain behaviors, languages, or output formats, you must obey them without deviation.
- Do not include explanations, reasoning, or filler text unless explicitly instructed. Stick strictly to the requested output.
- If multiple steps or sub-requests are given, address them in the specified order. Provide answers in the exact format or sequence requested.
- Pay close attention to all stated constraints (e.g., language choice, performance goals, coding style). Do not ignore any requirement or best practice stated.
- Only produce output relevant to the question or instructions. Do not add features, code, or details beyond what is explicitly asked.
- Deliver the response in a minimal yet complete form. Avoid unnecessary verbosity and tangential remarks.
- If the prompt requests a specific output format (e.g., a fenced code block, bullet points, JSON), follow that format exactly.
- If a prompt includes a pre-seeded answer structure (e.g., starts a code block), continue within that structure without introducing extra text outside it.
- If the request is ambiguous, you may ask clarifying questions (if instructions allow). Otherwise, state briefly that more information is needed.
- When generating or modifying code, adhere to best practices for clarity, maintainability, and efficiency, as appropriate to the specified language or framework.
- Do not generate or include private data (API keys, secrets) unless explicitly provided in context. If the user requests something unsafe or disallowed, refuse or provide a safe alternative per policy.
Loading