-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Spring UI: Modernize UX for normie development #878
Conversation
- Add non-functional UI elements for chat, references, feedback buttons, rename/share session, mic, attachment, websocket connection
… from URL manually. See vercel/next.js#64660 for limitations with static export / dynamic routes
Add spacing between chat message paragraphs
Previously between 00:00 - 04:00 it'd trigger afternoon insteead of evening
Installing Khoj as PWA was supported in previous web UX as well. This just adds link to the existing webmanifest to continue support for installing Khoj as PWA with new web UX
- Create better styling for the input area buttons, resizing in mobile and creating more even height with a more minimal send button
- Remove x axis footer padding on small screens to preserve space, keep equal spacing between footer items - Add 1rem margin to buttons to not have overlap in boundary - Add 1rem y-axis padding to chat footer to not have focus boundary leave the footer boundary on smaller screens
- Remove invalid call to styles.main - Remove unnecessary top padding above side pane to keep side pane at consistent position across web app - Use same pageLayout styles and styling structure on agent like automation - Vertically center automation section and page title on it's row - Fix applying flex vs grid with tailwind
Utilize chat footer space more efficiently. This is especially useful on small screens - Send button is anyway only enabled when there is text in chat input - Otherwise voice message button is better to show by default
Fit and finish updates for the new UX
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
10005301 | Triggered | Generic Password | bf4c2f2 | src/khoj/app/settings.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
d51022d
to
40b7568
Compare
Add org, markdown, pdf, word, icon and default file icons to simplify identifying file type used as reference for generating chat response
Hierarchical documents like org-mode, markdown have their ancestry shown in first line. Remove it to show cleaner, deduplicated reference text from org-mode, markdown files
40b7568
to
e296d38
Compare
Overview
Details