chore: Migrate to oxfmt

.github/ISSUE_TEMPLATE/bug_report.md

@@ -25,16 +25,16 @@ If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
 
--   OS: [e.g. iOS]
--   Browser [e.g. chrome, safari]
--   Version [e.g. 22]
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
 
 **Smartphone (please complete the following information):**
 
--   Device: [e.g. iPhone6]
--   OS: [e.g. iOS8.1]
--   Browser [e.g. stock browser, safari]
--   Version [e.g. 22]
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
 
 **Additional context**
 Add any other context about the problem here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,10 +2,10 @@
 
 _This section is optional if the PR is fully ready for review_
 
--   Create the PR as a "draft" PR
--   Add [WIP] to the title
--   Use the template below to ask for specific feedback
--   [ ] @name: Could you look at \_\_\_? I'm trying to do... (etc.)
+- Create the PR as a "draft" PR
+- Add [WIP] to the title
+- Use the template below to ask for specific feedback
+- [ ] @name: Could you look at \_\_\_? I'm trying to do... (etc.)
 
 # What
 
@@ -19,20 +19,20 @@ Replace this txt describing what kind of technical overlaying code changes were
 
 _This section is optional if there are no visible changes_
 
--   If possible add screenshots of the visible additions in the UI.
--   If there are changes in the UI, add **Before** and **After** Screenshots for quick overview.
--   If there was a Figma design, add a link to that here as well.
--   Hint : Drag and Drop any images you want to add to the PR. Also you can create a gif of an interactive version and add that!
+- If possible add screenshots of the visible additions in the UI.
+- If there are changes in the UI, add **Before** and **After** Screenshots for quick overview.
+- If there was a Figma design, add a link to that here as well.
+- Hint : Drag and Drop any images you want to add to the PR. Also you can create a gif of an interactive version and add that!
 
 # PR Checklist
 
--   [ ] Is your PR title following our conventional commit naming recommendations?
--   [ ] Have you filled in the PR Description Template?
--   [ ] Is your branch up to date with the latest in `main`?
--   [ ] Do the CI checks pass successfully?
--   [ ] Have you smoke tested the example applications?
--   [ ] Did you check that the changes meet accessibility standards?
--   [ ] Have you tested the application on these browsers?
-    -   [ ] Chrome (Fully supported)
-    -   [ ] Firefox (Major bug fixes supported)
-    -   [ ] Safari (Major bug fixes supported)
+- [ ] Is your PR title following our conventional commit naming recommendations?
+- [ ] Have you filled in the PR Description Template?
+- [ ] Is your branch up to date with the latest in `main`?
+- [ ] Do the CI checks pass successfully?
+- [ ] Have you smoke tested the example applications?
+- [ ] Did you check that the changes meet accessibility standards?
+- [ ] Have you tested the application on these browsers?
+    - [ ] Chrome (Fully supported)
+    - [ ] Firefox (Major bug fixes supported)
+    - [ ] Safari (Major bug fixes supported)

.oxfmtrc.json

@@ -0,0 +1,11 @@
+{
+    "$schema": "./node_modules/oxfmt/configuration_schema.json",
+    "printWidth": 120,
+    "trailingComma": "es5",
+    "tabWidth": 4,
+    "singleQuote": true,
+    "semi": true,
+    "singleAttributePerLine": true,
+    "sortPackageJson": false,
+    "ignorePatterns": ["dist", "pnpm-lock.yaml"]
+}

CODE_OF_CONDUCT.md

@@ -14,24 +14,24 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
--   Demonstrating empathy and kindness toward other people
--   Being respectful of differing opinions, viewpoints, and experiences
--   Giving and gracefully accepting constructive feedback
--   Accepting responsibility and apologizing to those affected by our mistakes,
-    and learning from the experience
--   Focusing on what is best not just for us as individuals, but for the
-    overall community
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
 
 Examples of unacceptable behavior include:
 
--   The use of sexualized language or imagery, and sexual attention or
-    advances
--   Trolling, insulting or derogatory comments, and personal or political attacks
--   Public or private harassment
--   Publishing others' private information, such as a physical or email
-    address, without their explicit permission
--   Other conduct which could reasonably be considered inappropriate in a
-    professional setting
+- The use of sexualized language or imagery, and sexual attention or
+  advances
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Our Responsibilities
 

CONTRIBUTING.md

@@ -8,25 +8,25 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 
 > And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
 >
-> -   Star the project
-> -   Tweet about it
-> -   Refer this project in your project's readme
-> -   Mention the project at local meetups and tell your friends/colleagues
+> - Star the project
+> - Tweet about it
+> - Refer this project in your project's readme
+> - Mention the project at local meetups and tell your friends/colleagues
 
 <!-- omit in toc -->
 
 ## Table of Contents
 
--   [Code of Conduct](#code-of-conduct)
--   [I Have a Question](#i-have-a-question)
--   [I Want To Contribute](#i-want-to-contribute)
-    -   [Reporting Bugs](#reporting-bugs)
-    -   [Suggesting Enhancements](#suggesting-enhancements)
-    -   [Your First Code Contribution](#your-first-code-contribution)
-    -   [Improving The Documentation](#improving-the-documentation)
--   [Styleguides](#styleguides)
-    -   [Commit Messages](#commit-messages)
--   [Join The Project Team](#join-the-project-team)
+- [Code of Conduct](#code-of-conduct)
+- [I Have a Question](#i-have-a-question)
+- [I Want To Contribute](#i-want-to-contribute)
+    - [Reporting Bugs](#reporting-bugs)
+    - [Suggesting Enhancements](#suggesting-enhancements)
+    - [Your First Code Contribution](#your-first-code-contribution)
+    - [Improving The Documentation](#improving-the-documentation)
+- [Styleguides](#styleguides)
+    - [Commit Messages](#commit-messages)
+- [Join The Project Team](#join-the-project-team)
 
 ## Code of Conduct
 
@@ -43,9 +43,9 @@ Before you ask a question, it is best to search for existing [Issues](https://gi
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
--   Open an [Issue](https://github.com/AllenInstitute/vis/issues/new).
--   Provide as much context as you can about what you're running into.
--   Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
+- Open an [Issue](https://github.com/AllenInstitute/vis/issues/new).
+- Provide as much context as you can about what you're running into.
+- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
 
 We will then take care of the issue as soon as possible.
 
@@ -63,16 +63,16 @@ We will then take care of the issue as soon as possible.
 
 A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
 
--   Make sure that you are using the latest version.
--   Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/AllenInstitute/vis/tree/main/docs). If you are looking for support, you might want to check [this section](#i-have-a-question)).
--   To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/AllenInstitute/visissues?q=label%3Abug).
--   Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
--   Collect information about the bug:
-    -   Stack trace (Traceback)
-    -   OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
-    -   Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
-    -   Possibly your input and the output
-    -   Can you reliably reproduce the issue? And can you also reproduce it with older versions?
+- Make sure that you are using the latest version.
+- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/AllenInstitute/vis/tree/main/docs). If you are looking for support, you might want to check [this section](#i-have-a-question)).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/AllenInstitute/visissues?q=label%3Abug).
+- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
+- Collect information about the bug:
+    - Stack trace (Traceback)
+    - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
+    - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
+    - Possibly your input and the output
+    - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
 
 <!-- omit in toc -->
 
@@ -82,16 +82,16 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
--   Open an [Issue](https://github.com/AllenInstitute/vis/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
--   Explain the behavior you would expect and the actual behavior.
--   Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good issue reports you should isolate the problem and create a reduced test case.
--   Provide the information you collected in the previous section.
+- Open an [Issue](https://github.com/AllenInstitute/vis/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Explain the behavior you would expect and the actual behavior.
+- Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good issue reports you should isolate the problem and create a reduced test case.
+- Provide the information you collected in the previous section.
 
 Once it's filed:
 
--   The project team will label the issue accordingly.
--   A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Issues with the `needs-repro` tag will not be addressed until they are reproduced.
--   If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
+- The project team will label the issue accordingly.
+- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Issues with the `needs-repro` tag will not be addressed until they are reproduced.
+- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
 
 ### Suggesting Enhancements
 
@@ -101,22 +101,22 @@ This section guides you through submitting an enhancement suggestion for Visuali
 
 #### Before Submitting an Enhancement
 
--   Make sure that you are using the latest version.
--   Read the [documentation](https://github.com/AllenInstitute/vis/tree/main/docs) carefully and find out if the functionality is already covered, maybe by an individual configuration.
--   Perform a [search](https://github.com/AllenInstitute/vis/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
--   Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
+- Make sure that you are using the latest version.
+- Read the [documentation](https://github.com/AllenInstitute/vis/tree/main/docs) carefully and find out if the functionality is already covered, maybe by an individual configuration.
+- Perform a [search](https://github.com/AllenInstitute/vis/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
 
 <!-- omit in toc -->
 
 #### How Do I Submit a Good Enhancement Suggestion?
 
 Enhancement suggestions are tracked as [GitHub issues](https://github.com/AllenInstitute/vis/issues).
 
--   Use a **clear and descriptive title** for the issue to identify the suggestion.
--   Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
--   **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
--   You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux.
--   **Explain why this enhancement would be useful** to most Visualization Toolkit users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
+- Use a **clear and descriptive title** for the issue to identify the suggestion.
+- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
+- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
+- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux.
+- **Explain why this enhancement would be useful** to most Visualization Toolkit users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
 
 ### Your First Code Contribution
 

README.md

@@ -8,10 +8,10 @@ This repository contains a collection of TypeScript libraries to help software e
 
 The following is the list of packages and their descriptions:
 
--   `vis-dzi`: A renderer for [Deep Zoom Images](https://en.wikipedia.org/wiki/Deep_Zoom)
--   `vis-geometry`: A collection of vector functions for 2D and 3D geometry
--   `vis-omezarr`: A renderer for [OME-Zarr](https://ngff.openmicroscopy.org/latest/) datasets
--   `vis-core`: A collection of useful utilities used to build our big-data, scalable, data visualization tools, including the DZI viewer, OME-Zarr viewer, and our scatterplot tool "Scatterbrain" for the [ABC Atlas](https://knowledge.brain-map.org/abcatlas) in the Brain Knowledge Platform web application
+- `vis-dzi`: A renderer for [Deep Zoom Images](https://en.wikipedia.org/wiki/Deep_Zoom)
+- `vis-geometry`: A collection of vector functions for 2D and 3D geometry
+- `vis-omezarr`: A renderer for [OME-Zarr](https://ngff.openmicroscopy.org/latest/) datasets
+- `vis-core`: A collection of useful utilities used to build our big-data, scalable, data visualization tools, including the DZI viewer, OME-Zarr viewer, and our scatterplot tool "Scatterbrain" for the [ABC Atlas](https://knowledge.brain-map.org/abcatlas) in the Brain Knowledge Platform web application
 
 We use [Semantic Versioning](https://semver.org/) for our packages. As of November 2024, all of them are in the `0.0.x` range, indicating that they are in early development.
 

biome.json

@@ -10,10 +10,7 @@
         "includes": ["**", "!**/dist/**/*", "!**/coverage/**/*", "!**/.astro/**/*", "!**/*.astro"]
     },
     "formatter": {
-        "enabled": true,
-        "indentStyle": "space",
-        "indentWidth": 4,
-        "lineWidth": 120
+        "enabled": false
     },
     "assist": {
         "actions": {
@@ -46,10 +43,5 @@
                 "noUselessElse": "error"
             }
         }
-    },
-    "javascript": {
-        "formatter": {
-            "quoteStyle": "single"
-        }
     }
 }