feat: update styles and add utility script for version tagging#50
feat: update styles and add utility script for version tagging#50phanimca wants to merge 18 commits intoThisIs-Developer:mainfrom
Conversation
- Changed body position to sticky for better header behavior. - Removed redundant syntax highlighting styles and replaced with a dark theme variable. - Removed mobile tabs section styles to streamline the CSS. - Updated mermaid diagram styles for better responsiveness and usability. - Introduced a new script `tag.sh` for calculating the next version tag based on Calendar Versioning. - Added a .gitignore file to exclude Salesforce DX files.
|
@phaniepam is attempting to deploy a commit to the ThisIs-Developer Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
UI Feedback
Requesting to fix this issue in the PR. |
- web/index.html, web/script.js, web/styles.css, web/assets/ — web app source - web/vercel.json — Vercel static hosting config with security headers - desktop-app/prepare.js — updated ROOT_DIR to point to web/ - package.json — updated dev script to serve from web/ Deploy on Vercel: set Root Directory to 'web' in project settings.
- Open button becomes a dropdown: Local File / SharePoint / Azure DevOps Repo - SharePoint: paste any direct file URL, fetches via browser (file must be publicly shared) - Azure DevOps: enter org/project/repo/branch/path + optional PAT (Code Read scope) - PAT transmitted only to dev.azure.com, never stored - Uses ADO REST API v7.1 with \=text for raw file content - Mobile menu has dedicated buttons for all three open options - Both modals show inline error messages and loading spinner while importing - Ctrl+O shortcut still opens local file picker
- add SharePoint/Azure DevOps import options with modals and validation - enforce HTTPS for SharePoint import and clear ADO PAT after attempts - upgrade frontend CDN dependencies (bootstrap, dompurify, mermaid, marked, mathjax, jsPDF, etc.) - bump Neutralino CLI usage to 11.7.1 - remove TOC/Note desktop header buttons - add Choose File header action and wire to existing file input - refactor header/toolbar/stats layout to prevent overlap and keep controls aligned
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
- Split monolithic web/script.js (2600 lines) into 10 ES modules in web/src/ - Replace CDN dependencies with npm packages (marked, mermaid, bootstrap, etc.) - Add Vite as build tool with optimized chunking for mermaid diagrams - Update desktop-app/prepare.js to use dist/ output from Vite - Move desktop-specific code to desktop-app/src/desktop-main.js - Add CLAUDE.md and AGENTS.md with updated architecture docs - Add claude-skills package for development workflows MathJax remains on CDN (config-based loading is simpler than bundling).
Add isEditorScrolling guard to syncPreviewClickToEditor to prevent interference when editor is mid-scroll from a previous sync operation.
- Add reload button to refresh externally modified files (Ctrl+R) - Fix Bootstrap dropdown initialization for ES modules - Make toolbar buttons icon-only at smaller widths (≤1399px) - Make view mode buttons (Editor/Split/Preview) icon-only responsively - Ensure file input is completely hidden - Compact dropzone on smaller screens
|
@copilot resolve the merge conflicts in this pull request |
|
@phanimca Hello, and thank you for your pull request—I really appreciate the idea and effort behind implementing support for:
These additions would be very valuable. However, since the repository has moved forward and several commits have already been merged and deployed, this pull request is now out of sync with the current codebase. As a result, there are conflicts across multiple files that are not straightforward to resolve at this stage. Could I kindly request that you create a new pull request based on the latest version of the Markdown view? That would make it much easier to review and integrate your changes. Thank you again for your contribution—this would be a great addition to the project. I appreciate your time and effort, and I look forward to your response. |
3 participants
tag.shfor calculating the next version tag based on Calendar Versioning.