PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p… by zulquer · Pull Request #69 · MultiSafepay/python-sdk

zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


zulquer · 2026-07-22T12:13:30Z

This PR fixes an issue in CartItem.add_tax_rate_percentage where converting the calculated tax rate ratio to a string via str(rating) could produce scientific exponential notation (such as '0E-10' or '1E-8') when handling Decimal objects with negative exponents.

When '0E-10' is sent in the API payload, it fails to match zero-tax rule keys (e.g. '0') in checkout_options.tax_tables.alternate, causing shopping cart validation errors.

…ercentage to prevent 0E-10

Copilot

Pull request overview

Fixes CartItem.add_tax_rate_percentage formatting so Decimal-derived tax selectors aren’t emitted in scientific notation (e.g. 0E-10 / 1E-8), which can break exact string matching against checkout_options.tax_tables.alternate keys during cart validation.

Changes:

Switches tax selector string conversion from str(Decimal) to fixed-point formatting via format(..., "f").
Refactors/expands unit tests to cover zero handling and scientific-notation edge cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`src/multisafepay/api/shared/cart/cart_item.py`	Uses fixed-point formatting for the computed tax ratio string.
`tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py`	Adds/renames tests for zero and Decimal exponent edge cases.

Comments suppressed due to low confidence (1)

tests/multisafepay/unit/api/shared/cart/test_unit_cart_item.py:214

This test currently only checks that scientific notation is absent and the value parses to zero, but it doesn’t assert the key format needed to match alternate tax table entries (e.g. name "0"). To cover the reported bug, assert the selector is exactly "0" for a quantized Decimal zero.

 item.add_tax_rate_percentage(scientific_zero)
assert "E" not in item.tax_table_selector
assert float(item.tax_table_selector) == 0.0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

+def test_add_tax_rate_percentage_zero():
 """Test that a 0.0 tax rate percentage is correctly set as the tax table selector in a CartItem."""
 item = CartItem()
 item.add_tax_rate_percentage(0.0)
 assert item.tax_table_selector == "0.0"


 # Use Decimal for precise division
 percentage_decimal = Decimal(str(tax_rate_percentage))
 rating = percentage_decimal / Decimal("100")
- self.tax_table_selector = str(rating)
+ self.tax_table_selector = format(rating, "f")
 except (ValueError, TypeError) as e:


PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

PTHMINT-133: Ensure fixed-point formatting in CartItem.add_tax_rate_p…
7d103c0
…ercentage to prevent 0E-10

zulquer requested a review from danielcivit July 28, 2026 12:26

danielcivit requested a review from Copilot July 29, 2026 14:30

Copilotstarted reviewing on behalf of danielcivit July 29, 2026 14:30 View session

CopilotAI reviewed Jul 29, 2026
View reviewed changes

danielcivit approved these changes Jul 30, 2026
View reviewed changes

danielcivit merged commit 58da201 into masterJul 30, 2026
6 checks passed

danielcivit deleted the PTHMINT-133 branch July 30, 2026 08:21

Uh oh!

Conversation

zulquer commented Jul 22, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

zulquer commented Jul 22, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

zulquer commented Jul 22, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

zulquer commented Jul 22, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

zulquer commented Jul 22, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes