Allowing no file in the PathProcessor

[andrade-leonardo]

In cases where the database record has the file field set to null, deleting the record will result in a type error in the $data field, as null is not an acceptable value at that moment.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.90%. Comparing base (f7052a5) to head (9a49833).
Report is 4 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master     #614      +/-   ##
============================================
+ Coverage     95.86%   95.90%   +0.04%     
- Complexity      110      111       +1     
============================================
  Files            11       11              
  Lines           290      293       +3     
============================================
+ Hits            278      281       +3     
  Misses           12       12              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[andrade-leonardo]

About the trailing comma errors, I'm open to fixing them if needed.

[gersonfs]

Same issue here. Occurs when removing a record where the field that would store the file name is null.

[ADmad]

Calling getPathProcessor() with a null value makes no sense. Instead the changes should be made to the calling method to simply not try getting the path processor if the db value is null.

[andrade-leonardo]

I made the change to no longer call the getPathProcessor() method as you suggested. I believe this is indeed more appropriate

[gersonfs]

@ADmad anything else we can contribute to get this PR approved?