Skip to content

Conversation

@bolinocroustibat
Copy link
Contributor

@bolinocroustibat bolinocroustibat self-assigned this Oct 1, 2025
Copy link
Contributor

@Pierlou Pierlou left a comment

Choose a reason for hiding this comment

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

The flow looks good to me, just wondering about the best wording, do we want to redirect to the /discussions for instance?

@bolinocroustibat
Copy link
Contributor Author

The flow looks good to me, just wondering about the best wording, do we want to redirect to the /discussions for instance?

I don't really have an opinion except maybe it's better to redirect the user to the index page as it's more expected, and it leaves choice to the user to go to the discussion tab or not?

Any suggestion to improve the wording @maudetes?
No hurry, anyway I won't merge this PR until Hydra's PR datagouv/hydra#341 is deployed on production - we don't want TabularAPI to be deployed with that by mistake when the DB is not migrated yet.

@bolinocroustibat bolinocroustibat force-pushed the dataset-id-in-410-error-message branch from 9de133e to 1be2acc Compare October 8, 2025 11:49
@bolinocroustibat bolinocroustibat changed the title feat: add info about dataset_id in the 410 error message when resource has been deleted feat: include dataset information in 410 error message for deleted resources Oct 8, 2025
Copy link
Contributor

@Pierlou Pierlou left a comment

Choose a reason for hiding this comment

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

Thanks 🙏

@bolinocroustibat bolinocroustibat merged commit 6f190bd into main Oct 8, 2025
4 checks passed
@bolinocroustibat bolinocroustibat deleted the dataset-id-in-410-error-message branch October 8, 2025 13:23
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.

3 participants