JavaWebStack / JavaWebStack/orm

Enhanced support for the @Deprecated annotation.

Open
#54 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
Many applications evolve over time and this also means that Models are getting deprecated and aren't used anymore. By supporting this annotation we introduce a clear way for the engineer and ORM to handle this.

**Describe the solution you'd like**

- The auto migrator should ignore the annotated models **if the table doesn't exist already**.
- The ORM model should still be functional, if the table exists else the methods do nothing/return empty.

**Describe alternatives you've considered**
Check the annotation myself and don't make calls to the ORM methods.

**Additional Context**
The annotation has the RUNTIME RetentionPolicy and is therefore accessible at runtime.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the auto migrator and ORM model entry points, then inspect how runtime annotations and missing tables are currently handled. Verify the requested behavior for deprecated models: existing tables remain usable, while absent tables are ignored and ORM methods do nothing or return empty results.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.