refactor(neon_framework): Cleanup settings and options related class names #1317
Conversation
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
…names Signed-off-by: jld3103 <[email protected]>
Leptopoda
reviewed
Dec 20, 2023
|
I still prefer AppImplementation over Client, but either way we should make the names consistent. If we change to Client later then we can do it, but these names are not aligned so that needs to be fixed first. |
provokateurin
deleted the
refactor/neon_framework/rename-settings-classes
branch
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.
Needed for #600
The
SpecificandAppparts were never needed in the class names. Also more aligned with the rest, usingAppImplementationinstead ofNextcloudApp.