I'm currently running into the following issue after upgrading to v5:
When having an event that has a startDate before the startDate of the scheduler, I get the following error:
nodrop.PNG (5.67 KiB) Viewed 597 times
I know this is an untranslated Bryntum validation but I don't understand what validation this is. Before the upgrade to v5, this action was just working without any errors. In what cases does this error occur now and how can I bypass it?
When letting go while this error shows, the drag action gets reverted.
I also noticed that in the same tooltip, the dates are shown twice.
Yes, that's because your locale miss a lot of required lines.
If you do not plan to localize all Scheduler, use our localization as a base, in that case you won't have such errors.
Here is the code that I applied to your demo to make it working
import { LocaleManager, LocaleHelper, ResourceModel, ResourceStore, Scheduler } from '@bryntum/scheduler';
import EnLocale from '@bryntum/scheduler/locales/scheduler.locale.En.js';
// ....
const currentLocale = {
localeName: 'current',
localeDesc: 'Current',
DateHelper: {
locale: 'nl-BE',
nonWorkingDays: {
0: true, // Sunday
6: true, // Saturday
},
},
};
// use EN locale as a base and apply required customization
const locale = LocaleHelper.mergeLocales(EnLocale, currentLocale);
LocaleManager.registerLocale('current', { locale : locale });
// Set the current Bryntum locale
void LocaleManager.applyLocale('current');
The line you see might be localized like this. Example from our De localization
EventDrag : {
noDropOutsideTimeline : 'Event wird möglicherweise nicht vollständig außerhalb der Timeline gelöscht'
},
// Enable missing localization Error throwing here to show how it can be used in end-user apps
// All non-localized strings which are in `L{foo}` format will throw runtime error
LocaleManager.throwOnMissingLocale = true;