Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: Double encoding of special characters during GET operations #509

Merged
merged 2 commits into from
Jan 5, 2025

Conversation

willguibr
Copy link
Member

@willguibr willguibr commented Jan 5, 2025

Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.

Description

Describe your changes in detail through motivation and context. Why is
this change required? What problem does it solve? If it fixes an open
issue, link to the issue using GitHub's closing issues keywords1.

Has your change been tested?

Explain how the change has been tested and what you ran to confirm your
change affects other parts of the code. Automated tests are generally
expected and changes without tests should explain why they aren't
required.

Screenshots (if appropriate):

Types of changes

What sort of change does your code introduce/modify?

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • This change is using publicly documented and stable APIs.

@willguibr willguibr self-assigned this Jan 5, 2025
@willguibr willguibr added the type/bug Something isn't working label Jan 5, 2025
@willguibr willguibr temporarily deployed to ZPA_BETA_TENANT01 January 5, 2025 17:05 — with GitHub Actions Inactive
@willguibr willguibr temporarily deployed to ZPA_PROD_TENANT01 January 5, 2025 17:05 — with GitHub Actions Inactive
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.66%. Comparing base (7fc8ef2) to head (f17c8f1).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #509    /-   ##
=======================================
  Coverage   68.66%   68.66%           
=======================================
  Files          92       92           
  Lines       19211    19213     2     
=======================================
  Hits        13191    13193     2     
  Misses       5228     5228           
  Partials      792      792           
Files with missing lines Coverage Δ
zpa/data_source_zpa_service_edge.go 71.51% <100.00%> ( 0.05%) ⬆️
zpa/data_source_zpa_service_edge_group.go 89.33% <100.00%> ( 0.01%) ⬆️
zpa/resource_zpa_service_edge_group.go 68.51% <100.00%> (ø)

@willguibr willguibr linked an issue Jan 5, 2025 that may be closed by this pull request
@willguibr willguibr merged commit 47a584a into master Jan 5, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
Status: 🚀 Shipped
Development

Successfully merging this pull request may close these issues.

Double encoding of special characters at SCIM operand validation
2 participants