Itsthatotherguy

export default function SessionsList() {
  const sessionsQuery = useSessionsListQuery();

  return (
    <PageLayout title="My sessions">
      {matchQueryStatus(sessionsQuery, {
        Loading: (
          <>
            <Skeleton height={70} mt={6} />
            <Skeleton height={70} mt={6} />

Itsthatotherguy

Quick examples

• feat: new feature
• fix(scope): bug in scope
• feat!: breaking change / feat(scope)!: rework API
• chore(deps): update dependencies

Commit types

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, libraries

Itsthatotherguy

This is a transcript of the messages I sent on the Slack channel.

Regarding the custom unit problem - The problem stems from a bug in the beautiful-dnd library. I can account for it but it's only a matter of time before they fix it, which will then break the functionality again. What do you reckon the right move is here?


The Draggable component has a prop - disableInteractiveElementBlocking. However, if you follow the code, you eventually arrive at this code block in their library:

export function PublicDraggable(props: PublicOwnProps) {
  // default values for props
  const isEnabled: boolean =