Exchange not allowing submission when Schedule has a conflict #339
+35
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ Deploy Preview for tts-fe-preview failed.
|
tomaspalma
requested changes
Nov 16, 2024
| import { Context, Dispatch, createContext, SetStateAction } from "react"; | ||
|
|
||
| interface ConflictsContextType { | ||
| conflictsSeverity: boolean; |
There was a problem hiding this comment.
Although in the CombinedProvider you are passing a number as the severity, here on the context you are still saying that this will be a boolean.
You need to change the type of the variable in the interface and in the createContext call
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #335
Makes the button disabled when Schedule has a severe conflict.