Skip to content

fix terminology#2966

Closed
sol-loup wants to merge 1 commit intomainfrom
fix-terminology
Closed

fix terminology#2966
sol-loup wants to merge 1 commit intomainfrom
fix-terminology

Conversation

@sol-loup
Copy link
Copy Markdown
Contributor

@sol-loup sol-loup commented Mar 25, 2025

Description

A term used in our code was not correct, as this does not transmit any data of the kind implied by the term. This is purely an error logging and simple logging system.

Type of change

Please delete options that are not relevant.

  • 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 not work as expected)

Screenshots

Please provide screenshots or snapshots of the system/state both before and after implementing the changes, if appropriate

Before

After

Test instructions

Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration.

Checklist

  • I followed general Pull Request best practices. Meta employees to follow this wiki
  • I have commented my code, particularly in hard-to-understand areas
  • I have added tests and all the new and existing unit tests pass locally with my changes
  • I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality.

Changelog entry

One liner entry to be surfaced in changelog.txt

@facebook-github-bot
Copy link
Copy Markdown
Contributor

@sol-loup has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Copy Markdown
Contributor

@sol-loup merged this pull request in 7196ea2.

SayanPandey pushed a commit to SayanPandey/facebook-for-woocommerce that referenced this pull request Apr 1, 2025
Summary:
## Description

A term used in our code was not correct, as this does not transmit any data of the kind implied by the term. This is purely an error logging and simple logging system.

### Type of change

Please delete options that are not relevant.

- [ ] 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 not work as expected)

## Screenshots
Please provide screenshots or snapshots of the system/state both before and after implementing the changes, if appropriate
### Before

### After

## Test instructions

Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration.

## Checklist

- [ ] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc))
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added tests and all the new and existing unit tests pass locally with my changes
- [ ] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality.

## Changelog entry

One liner entry to be surfaced in changelog.txt

Pull Request resolved: facebook#2966

Test Plan:
# Testing Completed:

1. Added logging statement to pageload
2. Logged FB API response and Request values.
3. Confirmed API is being hit (with correct API Token) when logger is called

[26-Mar-2025 00:01:44 UTC] Facebook API Request: Array
(
    [event] => test_log
    [event_type] => page_load
    [extra_data] => Array
        (
            [page] => connection_settings
            [timestamp] => 1742947304
        )

)

[26-Mar-2025 00:01:44 UTC] Facebook API Response: WooCommerce\Facebook\API\MetaLog\Response Object
(
    [raw_response_json:protected] => {"success":true}
    [response_data] => Array
        (
            [success] => 1
        )

)

Reviewed By: nrostrow-meta, nealweiMeta

Differential Revision: D71819581

Pulled By: sol-loup

fbshipit-source-id: 668ea86fcf6ad8e3ce902e59f3cee56b59149065
mradmeta pushed a commit that referenced this pull request Apr 14, 2025
Summary:
## Description

A term used in our code was not correct, as this does not transmit any data of the kind implied by the term. This is purely an error logging and simple logging system.

### Type of change

Please delete options that are not relevant.

- [ ] 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 not work as expected)

## Screenshots
Please provide screenshots or snapshots of the system/state both before and after implementing the changes, if appropriate
### Before

### After

## Test instructions

Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration.

## Checklist

- [ ] I followed general Pull Request best practices. Meta employees to follow this [wiki]([url](https://fburl.com/wiki/2cgfduwc))
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added tests and all the new and existing unit tests pass locally with my changes
- [ ] I have completed dogfooding and QA testing, or I have conducted thorough due diligence to ensure that it does not break existing functionality.

## Changelog entry

One liner entry to be surfaced in changelog.txt

Pull Request resolved: #2966

Test Plan:
# Testing Completed:

1. Added logging statement to pageload
2. Logged FB API response and Request values.
3. Confirmed API is being hit (with correct API Token) when logger is called

[26-Mar-2025 00:01:44 UTC] Facebook API Request: Array
(
    [event] => test_log
    [event_type] => page_load
    [extra_data] => Array
        (
            [page] => connection_settings
            [timestamp] => 1742947304
        )

)

[26-Mar-2025 00:01:44 UTC] Facebook API Response: WooCommerce\Facebook\API\MetaLog\Response Object
(
    [raw_response_json:protected] => {"success":true}
    [response_data] => Array
        (
            [success] => 1
        )

)

Reviewed By: nrostrow-meta, nealweiMeta

Differential Revision: D71819581

Pulled By: sol-loup

fbshipit-source-id: 668ea86fcf6ad8e3ce902e59f3cee56b59149065
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants