Conversation
…read in the JSON files.
… into correct directories, edited the html file to match figma design (without image)
have any formatting yet.
Basic Text display for bone set
Created a Python file for Flask, attempted to use HTMX, and tried to …
…nd displayed properly but still working on getting the annotations to be pulled and displayed properly.
dead buttons.
…ain and displayed the image from the data branch correctly.
…ain and displayed the image from the data branch correctly.
…ain and displayed the image from the data branch correctly. Also had to delete the directories we weren't using anymore.
…ain and displayed the image from the data branch correctly. Also had to delete the directories we weren't using anymore. Made it more dynamic in order to have it be less hardcoded for the future.
Addresses Issue #49.
…ic-ui-polish Implemented pop-up functionality for help modal.
…display-using-mock-data
…-annotation-display-using-mock-data Implement frontend mock data display for bone images and annotations
…ns (incl. Acetabulum)
…unctionality-with-htmx Search Feature Implemetation
- Update package.json to properly open app on port 5500 - Fix sidebar toggle functionality using getComputedStyle - Remove unused files: data_extraction/api.py, output.json, mock-bone-data.json 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
…tributing.md template with new cantact information
added good first issue template,tastcard template and updated the con…
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v3 | ||
|
|
||
| - name: Setup Node.js | ||
| uses: actions/setup-node@v3 | ||
| with: | ||
| node-version: '18' | ||
|
|
||
| - name: Install dependencies | ||
| run: npm install | ||
|
|
||
| - name: Run ESLint | ||
| run: npm run lint |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 7 months ago
To address this issue, we should add an explicit permissions block to the workflow. Since the jobs in the workflow merely checkout code, set up Node.js, install dependencies, and run ESLint—none of which require write access—the most restrictive sensible permission is contents: read. This block can be added at either the root of the workflow (applying to all jobs by default) or inside the job definition (affecting only the specific job). For simplicity and maintainability, adding it at the root is recommended. Update .github/workflows/lint.yml by inserting the following YAML block just after the workflow name (i.e., after line 1):
permissions:
contents: readNo additional methods, imports, or definitions are required.
| @@ -1,4 +1,6 @@ | ||
| name: Lint JavaScript | ||
| permissions: | ||
| contents: read | ||
|
|
||
| on: | ||
| push: |
all acceptance critteria met. 2 scripts for display logic and text labels plus documentations
|
cannot merge data branch to main |
adding annotation json files into data branch