Chore: Refactoring by renaming - #66
Merged
Merged
Conversation
samyuktaprabhu
force-pushed
the
chore/update-data-to-payload
branch
from
August 27, 2026 07:47
5a25ddf to
1e4f368
Compare
samyuktaprabhu
force-pushed
the
chore/update-data-to-payload
branch
from
August 27, 2026 07:50
1e4f368 to
a6ee4cf
Compare
samyuktaprabhu
marked this pull request as ready for review
August 27, 2026 08:57
There was a problem hiding this comment.
The changes look correct and consistent. All renamed identifiers (data → payload, ctxData; scalar → direct) are applied uniformly across production code, Javadoc, comments, and tests. No logic errors, bugs, or missed rename sites were found.
This is a clean, purely mechanical refactoring PR — the renaming improves naming clarity without introducing any correctness issues. No prior review comments exist and no new issues need to be raised.
PR Bot Information
Version: 1.29.52
- Correlation ID:
60365930-a1f5-11f1-95f9-8013cf857ca9 - Event Trigger:
pull_request.ready_for_review - File Content Strategy: Full file content
- LLM:
anthropic--claude-4.6-sonnet
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
♻️ Refactor: Rename
datatopayloadandscalartodirectin N8n PluginRefactor
♻️ Consistently renames the
dataparameter/variable topayloadthroughout the n8n plugin codebase and updatesscalarterminology todirectinInputExtractor, improving naming clarity and consistency across the module.Changes
N8nHandler.java: Renamed local variabledatatoctxDataand updated all usages inConditionEvaluator.evaluate()andInputExtractor.extract()calls.N8nServiceHandler.java: Updatedctx.get("data")toctx.get("payload")when retrieving the webhook payload from the event context, and fixed the corresponding Javadoc@paramdescription.N8nService.java: Renameddataparameter topayloadin bothtriggermethod signatures and their Javadoc@paramannotations.N8nServiceImpl.java: Renamed method parameterdatatopayloadand updatedctx.put("data", ...)toctx.put("payload", ...)when building the trigger event context. Updated Javadoc accordingly.InputExtractor.java: Renamed private methodgetAllScalarFieldsByKeytogetAllDirectFieldsByKey, updated internal variable names fromscalarFieldsByKeytodirectFieldsByKey, renamed private method parameterdatatonestedValuesByKeyingetNestedValue(), and updated all related comments and Javadoc from "scalar" to "direct".N8nServiceHandlerTest.java: Updated test mocks fromctx.get("data")toctx.get("payload")to align with the renamed event context key.PR Bot Information
Version:
1.29.52issue_comment.editede5852110-a1f6-11f1-9128-213126a1e6bf