Change Details

Before refactoring the code used to render content in `swh-web/browse`, we should add end to end tests to ensure no regression will appear. Notably, we should ensure that code highlighting will work correctly for a large set of programming languages and that special content type rendering implemented so far (pdf, mardown, Jupyter notebook, ...) are still functional.

Before refactoring the code used to render content in `swh-web/browse`, we should add end to end tests to ensure no regression will appear. Notably, we should ensure that code highlighting will work correctly for a large set of programming languages and that special content type rendering implemented so far (pdf, mardown, Jupyter notebook, ...) will still be functional.

Before refactoring the code used to render content in `swh-web/browse`, we should add end to end tests to ensure no regression will appear. Notably, we should ensure that code highlighting will work correctly for a large set of programming languages and that special content type rendering implemented so far (pdf, mardown, Jupyter notebook, ...) arewill still be functional.