-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
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
chore(front): Refactor code to follow eslint rules #7
Conversation
- typescript-eslint/no-unsafe-argument mostly fixed, but can't add type annotations for events in Svelte code - typescript-eslint/no-strict-null-check already fixed - typescript-eslint/no-unnecessary-type-assertion fixed in 0887210
Ignore mask_utils.ts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not comment on all type casting (const foo = bar as string - the as type part) but it should be avoided whenever we can. I think this article sums it up : https://dev.to/ylerjen/typescript-cast-is-a-type-breaker-1jbh
basicaly, if you cast a variable, you lose all confidence in TS. It sometimes means refactoring a bit though ! Let me know if you need some help !
Use the same ItemDetails interface for input and output API items
Rename for improved clarity
Restore deleted code
Fix opening source/view labels by default when only one source/view
Previously done in format_bbox function in backend format_bbox was deleted in #7 to keep same format between front and back
Previously done in format_bbox function in backend format_bbox was deleted in #7 to keep same format between front and back
Previously done in format_bbox function in backend format_bbox was deleted in pixano#7 to keep same format between front and back
Description
Refactor code to successfully pass eslint check with less rules disabled.
Changes
Added
Changed
Fixed