chore: run prettier on everything (#868)

Author: mvadari

.github/dependabot.yml

@@ -1,8 +1,8 @@
 version: 2
 updates:
-- package-ecosystem: pip
-  directory: "/"
-  schedule:
-    interval: monthly
-    time: "15:00"
-  open-pull-requests-limit: 10
+  - package-ecosystem: pip
+    directory: "/"
+    schedule:
+      interval: monthly
+      time: "15:00"
+    open-pull-requests-limit: 10

.github/workflows/faucet_test.yml

@@ -49,4 +49,3 @@ jobs:
 
       - name: Run Faucet tests
         run: poetry run poe test_faucet
-      

.github/workflows/publish_to_pypi.yml

@@ -2,106 +2,106 @@ name: Publish xrpl-py 🐍 distribution 📦 to PyPI
 on:
   push:
     tags:
-        - '*'
+      - "*"
 
 jobs:
   build:
     name: Build distribution 📦
     runs-on: ubuntu-latest
     env:
-        POETRY_VERSION: 2.1.1
+      POETRY_VERSION: 2.1.1
 
     steps:
-    - uses: actions/checkout@v4
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        # Use the lowest supported version of Python for CI/CD
-        python-version: "3.8"
-    - name: Load cached .local
-      id: cache-poetry
-      uses: actions/cache@v3
-      with:
+      - uses: actions/checkout@v4
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          # Use the lowest supported version of Python for CI/CD
+          python-version: "3.8"
+      - name: Load cached .local
+        id: cache-poetry
+        uses: actions/cache@v3
+        with:
           path: /home/runner/.local
           key: dotlocal-${{ env.POETRY_VERSION }}-${{ hashFiles('poetry.lock') }}
-    - name: Install poetry
-      if: steps.cache-poetry.outputs.cache-hit != 'true'
-      run: |
-        curl -sSL "https://install.python-poetry.org/" | python - --version "${{ env.POETRY_VERSION }}"
-        echo "${HOME}/.local/bin" >> $GITHUB_PATH
-        poetry --version || exit 1  # Verify installation
-    - name: Build a binary wheel and a source tarball
-      run: poetry build
-    - name: Store the distribution packages
-      uses: actions/upload-artifact@v4
-      with:
-        name: python-package-distributions
-        path: dist/
+      - name: Install poetry
+        if: steps.cache-poetry.outputs.cache-hit != 'true'
+        run: |
+          curl -sSL "https://install.python-poetry.org/" | python - --version "${{ env.POETRY_VERSION }}"
+          echo "${HOME}/.local/bin" >> $GITHUB_PATH
+          poetry --version || exit 1  # Verify installation
+      - name: Build a binary wheel and a source tarball
+        run: poetry build
+      - name: Store the distribution packages
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
   publish-to-pypi:
     name: >-
-        Publish Python 🐍 distribution 📦 to PyPI
-    needs: build  # Explicit dependency on build job
+      Publish Python 🐍 distribution 📦 to PyPI
+    needs: build # Explicit dependency on build job
     runs-on: ubuntu-latest
-    timeout-minutes: 10  # Adjust based on typical publishing time
+    timeout-minutes: 10 # Adjust based on typical publishing time
     permissions:
-        # More information about Trusted Publishing and OpenID Connect: https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/
-        id-token: write  # IMPORTANT: mandatory for trusted publishing
+      # More information about Trusted Publishing and OpenID Connect: https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/
+      id-token: write # IMPORTANT: mandatory for trusted publishing
     steps:
-    - name: Download all the dists
-      uses: actions/download-artifact@v4
-      with:
-        name: python-package-distributions
-        path: dist/
-    - name: Verify downloaded artifacts
-      run: |
-        ls dist/*.whl dist/*.tar.gz || exit 1
-    - name: Publish distribution 📦 to PyPI
-      uses: pypa/gh-action-pypi-publish@release/v1
-      with:
-        verbose: true
-        verify-metadata: true
+      - name: Download all the dists
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+      - name: Verify downloaded artifacts
+        run: |
+          ls dist/*.whl dist/*.tar.gz || exit 1
+      - name: Publish distribution 📦 to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          verbose: true
+          verify-metadata: true
 
   github-release:
     name: >-
-        Sign the Python 🐍 distribution 📦 with Sigstore
-        and upload them to GitHub Release
+      Sign the Python 🐍 distribution 📦 with Sigstore
+      and upload them to GitHub Release
     needs:
-    - publish-to-pypi
+      - publish-to-pypi
     runs-on: ubuntu-latest
-    timeout-minutes: 15  # Adjust based on typical signing and release time
+    timeout-minutes: 15 # Adjust based on typical signing and release time
 
     permissions:
-        contents: write  # IMPORTANT: mandatory for making GitHub Releases
-        id-token: write  # IMPORTANT: mandatory for sigstore
+      contents: write # IMPORTANT: mandatory for making GitHub Releases
+      id-token: write # IMPORTANT: mandatory for sigstore
 
     steps:
-    - name: Download all the dists
-      uses: actions/download-artifact@v4
-      with:
-        name: python-package-distributions
-        path: dist/
-    - name: Sign the dists with Sigstore
-      uses: sigstore/gh-action-sigstore-python@v2.1.1
-      with:
-        inputs: >-
+      - name: Download all the dists
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+      - name: Sign the dists with Sigstore
+        uses: sigstore/gh-action-sigstore-python@v2.1.1
+        with:
+          inputs: >-
             ./dist/*.tar.gz
             ./dist/*.whl
-    - name: Create GitHub Release
-      env:
-        GITHUB_TOKEN: ${{ github.token }}
-      run: >-
-            gh release create
-            '${{ github.ref_name }}'
-            --repo '${{ github.repository }}'
-            --generate-notes ||
-            (echo "::error::Failed to create release" && exit 1)
-    - name: Upload artifact signatures to GitHub Release
-      env:
-        GITHUB_TOKEN: ${{ github.token }}
-       # Upload to GitHub Release using the `gh` CLI.
-       # `dist/` contains the built packages, and the
-       # sigstore-produced signatures and certificates.
-      run: >-
-        gh release upload
-        '${{ github.ref_name }}' dist/**
-        --repo '${{ github.repository }}'
+      - name: Create GitHub Release
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        run: >-
+          gh release create
+          '${{ github.ref_name }}'
+          --repo '${{ github.repository }}'
+          --generate-notes ||
+          (echo "::error::Failed to create release" && exit 1)
+      - name: Upload artifact signatures to GitHub Release
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+          # Upload to GitHub Release using the `gh` CLI.
+          # `dist/` contains the built packages, and the
+          # sigstore-produced signatures and certificates.
+        run: >-
+          gh release upload
+          '${{ github.ref_name }}' dist/**
+          --repo '${{ github.repository }}'

.vscode/settings.json

@@ -31,10 +31,7 @@
       "source.organizeImports": "always"
     }
   },
-  "isort.args": [
-    "--profile",
-    "black"
-  ],
+  "isort.args": ["--profile", "black"],
   "python.testing.pytestEnabled": false,
   "python.testing.unittestEnabled": true
 }

CHANGELOG.md

@@ -8,26 +8,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [[Unreleased]]
 
 ### Fixed
+
 - Removed snippets files from the xrpl-py code repository. Updated the README file to point to the correct location on XRPL.org.
 
 ## [[4.3.0]] - 2025-07-29
 
 ### Added
+
 - Support for `Token Escrow` (XLS-85d)
 - Support for `NFTokenMintOffer` (XLS-52)
 - Support for `Permissioned DEX` (XLS-81)
 - Add warning messages to `MPTokenIssuanceCreate` and `VaultCreate` transaction as per [XLS-89d](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0089d-multi-purpose-token-metadata-schema).
 
-
 ## [4.2.0] - 2025-6-09
 
 ### Added
+
 - Improved validation for models to also check param types
 - Support for `Single Asset Vault` (XLS-65d)
 - Support for `Account Permission` and `Account Permission Delegation` (XLS-74d, XLS-75d)
 - Support for the `Batch` amendment (XLS-56d)
 
 ### Fixed
+
 - Add `MPTCurrency` support in `Issue` (rippled internal type)
 - Fix the implementation error in get_latest_open_ledger_sequence method. The change uses the "current" ledger for extracting sequence number
 - Increase default maximum payload size for websocket client
@@ -45,11 +48,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 
 - Support for `Deep Freeze` (XLS-77d)
-- Support for  `PermissionedDomains` (XLS-80)
+- Support for `PermissionedDomains` (XLS-80)
 - Support `AMMClawback` amendment (XLS-73d)
 - Support for the `simulate` RPC ([XLS-69](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0069d-simulate))
 
 ### Fixed
+
 - `Sign`, `SignFor`, and `SignAndSubmit` methods now properly handle WebSocket clients
 
 ## [4.0.0] - 2024-12-23
@@ -96,7 +100,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Add `nfts_by_issuer` clio-only API definition
 - Included `ctid` field in the `tx` request.
 - `from_xrpl` method accepts input dictionary keys exclusively in the proper XRPL format.
-- Support for  DynamicNFT amendment (XLS-46)
+- Support for DynamicNFT amendment (XLS-46)
 
 ### Fixed
 

CONTRIBUTING.md

@@ -94,13 +94,14 @@ docker run -dit -p 5005:5005 -p 6006:6006 --volume $PWD/.ci-config/:/etc/opt/rip
 ```
 
 Breaking down the command:
-* `docker run -p 5005:5005 -p 6006:6006` starts a Docker container with an open port for admin JsonRPC and WebSocket requests.
-* `-it` allows you to interact with the container.
-* `-d` runs the docker container in detached mode. The container will run in the background and developer gets back control of the terminal
-* `-t` starts a terminal in the container for you to send commands to.
-* `--volume $PWD/.ci-config:/etc/opt/ripple/` mounts the directories as indicated. It must be an absolute path, so we use `$PWD` instead of `./`. `rippled` software searches the location `/etc/opt/ripple/` (default behavior) for the config files. Hence there is no need to explicitly specify the config-file path.
-* `rippleci/rippled:develop` is an image that is regularly updated with the latest build of the `develop` branch of `rippled`.
-* `-a` starts `rippled` in standalone mode
+
+- `docker run -p 5005:5005 -p 6006:6006` starts a Docker container with an open port for admin JsonRPC and WebSocket requests.
+- `-it` allows you to interact with the container.
+- `-d` runs the docker container in detached mode. The container will run in the background and developer gets back control of the terminal
+- `-t` starts a terminal in the container for you to send commands to.
+- `--volume $PWD/.ci-config:/etc/opt/ripple/` mounts the directories as indicated. It must be an absolute path, so we use `$PWD` instead of `./`. `rippled` software searches the location `/etc/opt/ripple/` (default behavior) for the config files. Hence there is no need to explicitly specify the config-file path.
+- `rippleci/rippled:develop` is an image that is regularly updated with the latest build of the `develop` branch of `rippled`.
+- `-a` starts `rippled` in standalone mode
 
 Then to actually run the tests, run the command:
 
@@ -166,6 +167,7 @@ open index.html
 You can view docs builds for xrpl-py versions on the ReadTheDocs website here: https://readthedocs.org/projects/xrpl-py/builds/
 
 In order to test how a change in docs configuration looks like on ReadTheDocs before merging:
+
 1. Publish a branch with your docs configuration changes
 2. Active and hide the branch by scrolling down on this page: https://readthedocs.org/projects/xrpl-py/versions/
 3. View the page / build results here: https://readthedocs.org/projects/xrpl-py/builds/
@@ -188,13 +190,15 @@ Examples can be found in subfolders of [tests/integrations](https://github.com/X
 ## Updating `definitions.json` and models
 
 To update just the `definitions.json` file:
+
 ```bash
 poetry run poe definitions https://github.com/XRPLF/rippled/tree/develop
 ```
 
 Any Github branch link or local path to rippled will work here.
 
 To update the models as well:
+
 ```bash
 poetry run poe generate https://github.com/XRPLF/rippled/tree/develop
 ```
@@ -213,18 +217,19 @@ Verify that the changes make sense by inspection before submitting, as there may
 - Merge your changes.
 
 ### Release
+
 1. Please increment the version in `pyproject.toml` and update the `CHANGELOG.md` file appropriately. We follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 2. Please select a commit that is suitable for release and create a tag. The following commands can be helpful:
-`git tag -s -a <tag-title> -m "Optional Message describing the tag"`
-`git tag` -- This command displays all the tags in the repository.
-`git push <remote_name, e.g. upstream> tag <tag_title>`
+   `git tag -s -a <tag-title> -m "Optional Message describing the tag"`
+   `git tag` -- This command displays all the tags in the repository.
+   `git push <remote_name, e.g. upstream> tag <tag_title>`
 3. A [Github Workflow](.github/workflows/publish_to_pypi.yml) completes the rest of the Release steps (building the project, generating a .whl and tarball, publishing on the PyPI platform). The workflow uses OpenID Connect's temporary keys to obtain the necessary PyPI authorization.
-As a prerequisite, the PyPI `xrpl-py` project needs to authorize Github Actions as a "Trusted Publisher". This page contains helpful resources: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#configuring-trusted-publishing
+   As a prerequisite, the PyPI `xrpl-py` project needs to authorize Github Actions as a "Trusted Publisher". This page contains helpful resources: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#configuring-trusted-publishing
 4. Send an email to [xrpl-announce](https://groups.google.com/g/xrpl-announce).
 5. Post an announcement in the [XRPL Discord #python channel](https://discord.com/channels/886050993802985492/886053080913821717) with a link to the changes and highlighting key changes.
 
-
 **Note: If maintainers prefer to manually release the xrpl-py software distribution, the below steps are relevant.**
+
 1. Create a branch off main that properly increments the version in `pyproject.toml` and updates the `CHANGELOG` appropriately. We follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 2. Merge this branch into `main`.
 3. Locally build and download the package.