Fixes reference errors after dependency upgrades #46
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
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.
flyteorg/flyte#182
The update to @date-io/moment made it incompatible with
moment.utcdue to a direct reference made to.weekdaysShort, which won't exist on the object we are passing. (See this change)For now, I've fixed the version to the last known working version. We can do an explicit update to the latest version later on, as it will also involve updating material-pickers.
flyteorg/flyte#179
d3-dagmade some backwards incompatible renames between 0.1 and 0.2. I updated our local type definitions and the reference todratify.