Applied !MR 60 as a patch against Smart Date 4.2.0 but it did not resolve my issue - still received a validation error message about untranslatable fields.
Applied #128 🐛 New non translatable field on translatable content throws error Needs work against core 10.3.7 and an unpatched copy of Smart Date 4.2.0 and did not receive a validation error.
Applied !MR 60 as a patch against Smart Date 4.2.0 but it did not resolve my issue - still received a validation error message about untranslatable fields.
Confirming that applying #128 🐛 New non translatable field on translatable content throws error Needs work against core 10.3.7 and an unpatched copy of Smart Date 4.2.0 resulted in no validation error on my smart_date field.
Also tested the MR against 8.x-3.0 branch and was able to add additional query filtering on the JsonApiQueryEvent, which was successful in returning the appropriate entities on the Pull Form.
Would like this to be able to be extended past the Pull Form/ implemented in the Import Service as suggested in #19 so submodules like Entity Share Cron can also make use of the JsonApiQueryEvent to allow users to implement the same altered filtering on cron.