📝 docs: Update readMe and comments.

README.md

@@ -551,7 +551,8 @@ Example of a Mapping Job definition file with csv source type:
       "sourceBinding": {
         "patient": {
           "jsonClass": "FileSystemSource",
-          "path": "patients.csv"    
+          "path": "patients.csv",
+          "contentType": "csv"
         }
       }
     },
@@ -560,7 +561,8 @@ Example of a Mapping Job definition file with csv source type:
       "sourceBinding": {
         "practitioner": {
           "jsonClass": "FileSystemSource",
-          "path": "practitioners.csv"
+          "path": "practitioners.csv",
+          "contentType": "csv"
         }
       }
     }
@@ -649,7 +651,6 @@ The json snippet above illustrates the structure of an example mapping job in st
 Similar to the batch mode, most of the fields are the same. The only differences are:
 - `asStream` field in the source settings
 - `path`  in the source binding of the mapping. `path` should be the name of the **folder** this time, and it is where toFHIR will monitor the changes.
-- `contentType` in the source binding of the mapping. `contentType` field is mandatory.
 
 ##### SQL
 
@@ -1001,7 +1002,8 @@ Or you can use a local file system to persist the generated FHIR resources:
 {
   "sinkSettings": {
     "jsonClass": "FileSystemSinkSettings",
-    "path": "sink/project1"
+    "path": "sink/project1",
+    "contentType": "csv"
   }
 }
 ```

tofhir-engine/src/main/scala/io/tofhir/engine/model/FhirMappingTask.scala

@@ -42,6 +42,8 @@ trait MappingSourceBinding extends Serializable {
  * field. It reads the files with the specified content type in the given folder.
  *
  * Example for Batch Jobs:
+ *   - With extension in path:
+ *     FileSystemSource(path = "data/patients.csv") => Will read the "data/patients.csv" file.
  *   - Providing folder name and content type:
  *     FileSystemSource(path = "data/patients", contentType = "csv") => Will read all files in the "data/patients" folder and interpret them as a csv.
  *