-
Notifications
You must be signed in to change notification settings - Fork 2.7k
added multiple query properties #4041
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
base: main
Are you sure you want to change the base?
added multiple query properties #4041
Conversation
df37a4c
to
1f408ec
Compare
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.
I've left some comments that should be addressed.
On top of that, we need to do changes in DeleteHistoricCaseInstancesUsingBatchesCmd
, BatchDeleteCaseConfig
, DeleteHistoricProcessInstancesUsingBatchesCmd
and BatchDeleteProcessConfig
in order to add the new methods.
...able-cmmn-api/src/main/java/org/flowable/cmmn/api/history/HistoricPlanItemInstanceQuery.java
Outdated
Show resolved
Hide resolved
...flowable-cmmn-engine/src/main/resources/org/flowable/cmmn/db/mapping/entity/CaseInstance.xml
Outdated
Show resolved
Hide resolved
...-cmmn-engine/src/main/resources/org/flowable/cmmn/db/mapping/entity/HistoricCaseInstance.xml
Outdated
Show resolved
Hide resolved
...able-cmmn-engine/src/test/java/org/flowable/cmmn/test/runtime/CaseInstanceQueryImplTest.java
Outdated
Show resolved
Hide resolved
...n-engine/src/test/java/org/flowable/cmmn/test/history/HistoricCaseInstanceQueryImplTest.java
Outdated
Show resolved
Hide resolved
...lowable-engine/src/main/resources/org/flowable/db/mapping/entity/HistoricProcessInstance.xml
Outdated
Show resolved
Hide resolved
...-cmmn-engine/src/main/resources/org/flowable/cmmn/db/mapping/entity/HistoricCaseInstance.xml
Outdated
Show resolved
Hide resolved
...lowable-engine/src/main/resources/org/flowable/db/mapping/entity/HistoricProcessInstance.xml
Outdated
Show resolved
Hide resolved
...vice/src/main/resources/org/flowable/task/service/db/mapping/entity/HistoricTaskInstance.xml
Outdated
Show resolved
Hide resolved
...vice/src/main/resources/org/flowable/task/service/db/mapping/entity/HistoricTaskInstance.xml
Outdated
Show resolved
Hide resolved
modules/flowable-engine/src/test/java/org/flowable/engine/test/api/task/TaskQueryTest.java
Outdated
Show resolved
Hide resolved
...task-service/src/main/java/org/flowable/task/service/impl/HistoricTaskInstanceQueryImpl.java
Outdated
Show resolved
Hide resolved
modules/flowable-task-service/src/main/java/org/flowable/task/service/impl/TaskQueryImpl.java
Outdated
Show resolved
Hide resolved
489df0c
to
8411991
Compare
added query parameter for case, processes, tasks, plan items and the historic variants changes according to comments fixed testcases
8411991
to
e7cf41f
Compare
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.
I've added one more comment, there is some duplicated code.
Apart from that the ProcessInstanceQueryTest
and HistoricActivityInstanceTest
, from what I can see, are going to pass even if you do not do any query in the mybatis XML. I think that we should have more data and validate that we are only getting part of the data
added query parameter for case, processes, tasks, plan items and the historic variants
Check List: