We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In TimelineContext file there is a check on range validity which causes the component to crash if a invalid start or end is passed to konva-timeline.
TimelineContext
const range = useMemo((): InternalTimeRange => { const { start: externalStart, end: externalEnd } = externalRange; const start = getValidTime(externalStart, timezone); const end = getValidTime(externalEnd, timezone); return { start, end }; }, [externalRange, timezone]);
Try fixing the issue adding a call to onErrors when there is something wrong. The goal is to avoid the component to crash.
onErrors
The text was updated successfully, but these errors were encountered:
feat: 🎸 [KonvaTimeLine]Added Range validation
7b601d4
✅ Closes: #138
chore(release): 1.16.0 [skip ci]
58b0bfa
# [1.16.0](v1.15.4...v1.16.0) (2023-10-27) ### Features * 🎸 [KonvaTimeLine]Added Range validation ([7b601d4](7b601d4)), closes [#138](#138)
🎉 This issue has been resolved in version 1.16.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
CrisGrud
Successfully merging a pull request may close this issue.
In
TimelineContext
file there is a check on range validity which causes the component to crash if a invalid start or end is passed to konva-timeline.Try fixing the issue adding a call to
onErrors
when there is something wrong.The goal is to avoid the component to crash.
The text was updated successfully, but these errors were encountered: