Comments (3)
I thought this would be easy. However, they changed a lot of code. My approach with copying the old classes did not work. They also removed the com.intellij.codeInsight.daemon.impl.quickfix.SideEffectWarningDialog
class, see: https://github.com/mapstruct/mapstruct-idea/actions/runs/6916833362/job/18817324564
It is still only in the LATEST-EAP-SNAPSHOT
, will be likely in main with 2023.3
though.
I think we should either:
- ignore the failure in the github actions for now
- when 2023.3 is released: maybe disable the
WrongUsageOfMappersFactoryInspection
(not the most important intention)
I am not sure what happens when we switch to 2023.3 as the main version for development. I think this intention cannot run on older versions then? Or does it just not build with that version? We'll see.
from mapstruct-idea.
I had a look at it. They didn't remove it. They just changed it. They are now doing:
return new RemoveUnusedVariableFix(variable).asIntention();
I've done PR #162 for this
from mapstruct-idea.
Related Issues (20)
- Support chained mapping composition HOT 2
- Use `unmappedTargetPolicy` in the unmapped target properties inspection
- Support for completion and Go To Definition within Mapping#qualifiedByName - for shared configurations HOT 5
- when I enable the plugin, the target class is different from the one when I disable the plugin HOT 1
- java.lang.ClassCastException: Object of type Address can't be cast to CompositeTracker HOT 1
- Support the '-Amapstruct.unmappedTargetPolicy' config of maven-compiler-plugin HOT 1
- Rework `@InheritConfiguration` and support auto-inheritance
- Fix workaround for getting the mockJDK annotations.jar in the gradle build HOT 1
- Code completion doesn't work with lombok @SuperBuilder annotation HOT 3
- Unmapped target properties warning is missing if source is a Java record HOT 5
- Auto completion for InheritConfiguration#name, InheritInverseConfiguration#name HOT 1
- Disable unmapped target property warnings when implicitly mapping from a map HOT 2
- Completion for properties don't work (both target and source) HOT 2
- Array and Map paramter ignored as source-parameter if used as only source
- Java expression HOT 1
- Report Non-existing target properties as errors HOT 1
- WrongUsageOfMappersFactoryInspection ignores if componentModel is defined in MapperConfig HOT 1
- IDE Support of `BeanMapping#ignoredTargets`
- Code Completion didn't work well. HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mapstruct-idea.