jalameta / jps-support Goto Github PK

Problem

this method is conflicted with build in method that handle exception. We can't override from children's class due to incompatible method signature from BaseJob and we never get the compatibility with the given Laravel documentation above.

Solution

We should change the current method name to another name.

Impact

The code that calls $job->failed() should be changed and this will completely be breaking change.

Instead of using thirdparty package for uuid, maybe we should consider using built-in laravel UUID creation, Str::uuid() and/or Str::orderedUuid().

Acceptance Criteria

• DeleteAnIndex process/job that should be queued.
• Should be determined in the model with the method shouldDeleteIndex()

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for jalameta/jps-support ^0.1.12 -> satisfiable by jalameta/jps-support[v0.1.12].
- Conclusion: remove ramsey/uuid 4.0.1
- Conclusion: don't install ramsey/uuid 4.0.1
- jalameta/jps-support v0.1.12 requires ramsey/uuid ^3.8 -> satisfiable by ramsey/uuid[3.8.0, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.x-dev].
- Can only install one of: ramsey/uuid[3.8.0, 4.0.1].
- Can only install one of: ramsey/uuid[3.9.0, 4.0.1].
- Can only install one of: ramsey/uuid[3.9.1, 4.0.1].
- Can only install one of: ramsey/uuid[3.9.2, 4.0.1].
- Can only install one of: ramsey/uuid[3.9.3, 4.0.1].
- Can only install one of: ramsey/uuid[3.x-dev, 4.0.1].
- Installation request for ramsey/uuid (locked at 4.0.1) -> satisfiable by ramsey/uuid[4.0.1].

When booting this trait , while also checking the application environment and global config setting, there should be a method within the model to determine if the current data should be indexed.

add granularity to elastic search index.

• DAILY
• MONTHLY
• WEEKLY