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

Remove abstract pre/postprocess from BaseModel #123

Merged
merged 2 commits into from
Mar 10, 2025

Conversation

JakubGonera
Copy link
Contributor

Description

Remove abstract pre/postprocess methods from BaseModel in native Android code. The methods are always called on concrete classes so it's not necessary for them to be abstract.

Type of change

  • 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)
  • Documentation update (improves or adds clarity to existing documentation)

Tested on

  • iOS
  • Android

Checklist

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation accordingly
  • My changes generate no new warnings

@JakubGonera JakubGonera requested a review from chmjkb March 10, 2025 10:24
Copy link
Contributor

@chmjkb chmjkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@JakubGonera JakubGonera force-pushed the @jakubgonera/remove-abstract-pre-post-process branch from bcac318 to 59e2fbf Compare March 10, 2025 11:37
@JakubGonera JakubGonera merged commit 19e23ac into main Mar 10, 2025
2 checks passed
@JakubGonera JakubGonera deleted the @jakubgonera/remove-abstract-pre-post-process branch March 10, 2025 11:57
JakubGonera added a commit that referenced this pull request Mar 12, 2025
## Description
Remove abstract pre/postprocess methods from BaseModel in native Android
code. The methods are always called on concrete classes so it's not
necessary for them to be abstract.

### Type of change
- [ ] 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)
- [ ] Documentation update (improves or adds clarity to existing
documentation)

### Tested on
- [ ] iOS
- [x] Android

### Checklist
- [x] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [x] My changes generate no new warnings

---------

Co-authored-by: Jakub Gonera <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants