-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
chore: Remove deprecated unused fields #29831
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
57 changes: 0 additions & 57 deletions
57
app/server/appsmith-server/src/main/java/com/appsmith/server/domains/Organization.java
This file was deleted.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The search results show that
datasourceStorage.getWorkspaceId()
is being used in the codebase to setworkspaceId
properties, which aligns with the transition from organizations to workspaces. However, the usage inCreateDBTablePageSolutionCEImpl.java
is inconsistent with this pattern, as it usesorganizationId
andorgId
keys with workspace IDs as their values.Given this information, it appears that the usage in
CreateDBTablePageSolutionCEImpl.java
may need to be reviewed to ensure it is consistent with the rest of the codebase and the transition to workspaces. It's possible that these keys are retained for backward compatibility with analytics or other systems, but this should be confirmed.The findings suggest that there may be an issue with the usage of
organizationId
inCreateDBTablePageSolutionCEImpl.java
, and it should be verified whether this is intentional for backward compatibility or an oversight that needs correction.Analysis chain
Ensure that there are no remaining references to the removed
organizationId
field in the codebase, including database queries and any serialization/deserialization logic that may have depended on this field.The search for references to
organizationId
in the codebase has returned multiple hits. Each of these needs to be examined to determine if they are part of the deprecated functionality that should have been removed or if they are valid in the current context of the codebase.Given the output, it seems that
organizationId
is still being used in various places in the codebase. However, without more context about each usage, it's not possible to definitively say whether these are issues that need to be addressed or if they are acceptable uses oforganizationId
. For example, the references in migration scripts or in classes that have not been refactored yet might be expected.To proceed, we need to examine a few of these instances to understand their context. Let's start by looking at the references in
FieldNameCE.java
,Action.java
, andCreateDBTablePageSolutionCEImpl.java
to see if they are part of the deprecated functionality.The references to
organizationId
inFieldNameCE.java
andAction.java
are marked as deprecated, which is consistent with the PR's objective to phase out such fields. However, the usage inCreateDBTablePageSolutionCEImpl.java
is ambiguous because it usesorganizationId
as a key but assigns it a workspace ID value, which could either be intentional for backward compatibility or an oversight.To clarify the usage in
CreateDBTablePageSolutionCEImpl.java
, we need to investigate whether the key name should be updated toworkspaceId
to match the value being assigned fromdatasourceStorage.getWorkspaceId()
.The context from
CreateDBTablePageSolutionCEImpl.java
shows thatdatasourceStorage.getWorkspaceId()
is being assigned to keys namedorganizationId
andorgId
. This suggests that the keys might be retained for backward compatibility. However, without additional context, it's not clear if this is the correct approach or if it's an oversight.To gain a better understanding, we should look for additional usages of
datasourceStorage.getWorkspaceId()
to see if it is consistently being used in place oforganizationId
and whether the key names have been updated elsewhere in the codebase.Scripts Executed
The following scripts were executed for the analysis:
Script:
Length of output: 2528
Script:
Length of output: 1825
Script:
Length of output: 937
Script:
Length of output: 6852
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's used for analytics. Changing that would mean potentially breaking our analytics, and renaming that may not be worth the trouble.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sharat87 Understood, the usage of
organizationId
for analytics purposes will remain as is to ensure stability. No further action is required on this matter. If there's anything else that needs attention, please let me know.If you found this review helpful, would you consider giving us a shout-out on X?
Thank you for using CodeRabbit!