Skip to content

Feat: differentiate notebook view#332

Merged
cristian-tamblay merged 2 commits into
developfrom
feat/differentiate-notebooks-view
Oct 20, 2025
Merged

Feat: differentiate notebook view#332
cristian-tamblay merged 2 commits into
developfrom
feat/differentiate-notebooks-view

Conversation

@Creylay
Copy link
Copy Markdown
Collaborator

@Creylay Creylay commented Oct 15, 2025

Summary

Improve visual differentiation between dataset and notebook views by displaying the associated dataset name in the notebook preview title. This change helps users quickly identify which dataset a notebook is linked to, reducing confusion between similar-looking views.

Type of change

  • Front end new feature.

Changes

  • Modified DatasetPreviewNotebook component to display dataset name instead of generic "Dataset Preview"
  • Added getDatasetName() function to resolve dataset name from notebook.dataset_id
  • Updated Typography to show "[Dataset Name] Preview" format
  • Improved contextual clarity for notebook-dataset relationships

How to Test

  1. Navigate to Notebooks page
  2. Select any notebook that has an associated dataset
  3. Verify the preview title shows "[Dataset Name] Preview" instead of generic "Dataset Preview"
  4. Confirm the dataset name displayed matches the actual associated dataset
  5. Test with notebooks linked to different datasets to ensure correct name resolution

Notes

This enhancement addresses user confusion between dataset and notebook views by providing immediate visual context about which dataset the notebook is processing. The title now clearly indicates the relationship between the notebook and its source dataset.

@cristian-tamblay cristian-tamblay merged commit 77f8ba0 into develop Oct 20, 2025
5 checks passed
@cristian-tamblay cristian-tamblay deleted the feat/differentiate-notebooks-view branch October 20, 2025 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants