Fix/beta 3 extractions list #1199
Open
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
…s to fix rendering of extraction events bugs.
avoids random startup failures on macs.
|
@lmarini I am taking a look. Looks like the extraction history is fixed, checking over the code now. |
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.
Several fixes required for beta-3 release, mostly in the listing of extractor events. This also cleans up a lot of code and combines useEffects calls in one call instead of many. Now the list of extraction events should be scoped to the dataset or file id currently being looked at, instead of showing all events. Also worth noticing, extraction messages were not working due to a change in imports. Please see comments on commits for a full list.