Tag: Branch: Tree: 0a2d9b3b54

edge

master

0.1.0

0.2.0

0.3.0

0.4.0

0.5.0

0.6.0

0.6.1

0.7.0

0.7.1

0.7.2

0.7.3

0.7.4

0.8.0

0.8.1

0.9.0

0.9.1

0.9.2

0.9.3

0.9.4

1.0.0

1.1.0

1.1.1

1.1.2-beta

1.1.3-beta

1.10.0

1.10.1

1.10.2

1.11.0

1.11.1

1.11.2

1.12.0

1.13.0

1.13.1

1.14.0

1.14.1

1.14.2

1.14.3

1.15.0

1.15.1

1.15.2

1.15.3

1.16.0

1.16.1

1.16.2

1.17.0

1.18.0

1.18.1

1.19.0

1.19.1

1.19.2

1.2.0

1.3.0-beta

1.3.1-beta

1.3.2-beta

1.4.0

1.5.0

1.6.0

1.6.1

1.6.2

1.6.3

1.7.0

1.8.0

1.9.0

latest

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '0a2d9b3b54'

${ noResults }

Commit Graph

1 Commits (0a2d9b3b54ee51a3965d79c68409ef045ad5834b)

Author	SHA1	Message	Date
Marien Fressinaud	15505a0377	tec: Refactor the export feature (#3045) ... Even if the issue #3035 seemed pretty simple at a first glance, it was more complicated than I expected. Because we send CSP headers AFTER running the controller actions, it means we can't "echo" any content from the controller. It's in fact a good practice, but it was easier at the time we developed the feature. To fix that, the only thing I had to do was to move the `print()` and `readfile()` function into the view. The problem was that we needed to output the content from the CLI too. Then, things became more complicated. I decided to extract the export-related methods in a `FreshRSS_Export_Service` class, in order to use it from both the controller and the CLI. It was an opportunity to refactor the whole feature in order to make it a bit more linear and easy to read. Reference: https://github.com/FreshRSS/FreshRSS/issues/3035	4 years ago