Skip to content

[GSK-1576] Make "go back" available with shuffle mode in Dataset Explorer#1329

Merged
andreybavt merged 3 commits intomainfrom
feature/gsk-1576-cant-go-back-in-shuffle-mode
Aug 25, 2023
Merged

[GSK-1576] Make "go back" available with shuffle mode in Dataset Explorer#1329
andreybavt merged 3 commits intomainfrom
feature/gsk-1576-cant-go-back-in-shuffle-mode

Conversation

@henchaves
Copy link
Copy Markdown
Member

Description

This PR makes the previous data point available while the shuffle mode is on in the Dataset Explorer (Debugger tab). Previously, it was not able to move back to the previous data point when the shuffle mode was on.

Related Issue

GSK-1576 (available on Linear)

  • 📚 Examples / docs / tutorials / dependencies update
  • 🔧 Bug fix (non-breaking change which fixes an issue)
  • 🥂 Improvement (non-breaking change which improves an existing feature)
  • 🚀 New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 🔐 Security fix

@henchaves henchaves self-assigned this Aug 24, 2023
@linear
Copy link
Copy Markdown

linear Bot commented Aug 24, 2023

const percentRegressionUnit = ref(true);

const canPrevious = computed(() => !shuffleMode.value && rowNb.value > 0);
const canPrevious = computed(() => rowNb.value > 0);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how will it work if previous does rowNb.value -= 1; and it'll mean that instead of going to a previous example you saw earlier you'd go to an example with a row number = current - 1?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andreybavt it's already doing that, because the data points come from backend already shuffled. To get the exactly previous data point of the original order we could use the property _GISKARD_INDEX_ instead of rowNb

Copy link
Copy Markdown
Member Author

@henchaves henchaves Aug 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, to wrap up, the behaviour of rowNb.value -= 1 (current behaviour) is to go back to the last data point seen instead of the datapoint with _GISKARD_INDEX_ - 1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it thanks

@henchaves henchaves requested review from AbSsEnT, Googleton, andreybavt and mathieuroques and removed request for AbSsEnT, Googleton and mathieuroques August 24, 2023 10:04
@sonarqubecloud
Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@andreybavt andreybavt merged commit c1668d6 into main Aug 25, 2023
@Hartorn Hartorn deleted the feature/gsk-1576-cant-go-back-in-shuffle-mode branch September 22, 2023 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants