Fix RSS issues #720

Fusionado
papey fusionados 2 commits de fix/#673-date-id-rss en master hace 4 años
papey comentado hace 4 años (Migrado desde github.com)

Here is a PR relative to issue #673.

At this state, the PR adds id and published field for each blog entry inside the RSS feed.

I'm not sure but it's look like there is no method or field attached to post struct to get information about update metadata.

I can add this but I want to be sure that it's in the scope of this PR.

Thanks for you're reply.

Here is a PR relative to issue #673. At this state, the PR adds `id` and `published` field for each blog entry inside the RSS feed. I'm not sure but it's look like there is no method or field attached to `post` struct to get information about update metadata. I can add this but I want to be sure that it's in the scope of this PR. Thanks for you're reply.
codecov[bot] comentado hace 4 años (Migrado desde github.com)

Codecov Report

Merging #720 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #720      +/-   ##
==========================================
- Coverage    39.3%   39.29%   -0.01%     
==========================================
  Files          72       72              
  Lines        9534     9536       +2     
  Branches     2275     2275              
==========================================
  Hits         3747     3747              
- Misses       4714     4716       +2     
  Partials     1073     1073
# [Codecov](https://codecov.io/gh/Plume-org/Plume/pull/720?src=pr&el=h1) Report > Merging [#720](https://codecov.io/gh/Plume-org/Plume/pull/720?src=pr&el=desc) into [master](https://codecov.io/gh/Plume-org/Plume/commit/458baf5f78daec1b823e0bbd17eaa96c23ae92f8?src=pr&el=desc) will **decrease** coverage by `<.01%`. > The diff coverage is `0%`. ```diff @@ Coverage Diff @@ ## master #720 +/- ## ========================================== - Coverage 39.3% 39.29% -0.01% ========================================== Files 72 72 Lines 9534 9536 +2 Branches 2275 2275 ========================================== Hits 3747 3747 - Misses 4714 4716 +2 Partials 1073 1073 ```
epsilon-phase comentado hace 4 años (Migrado desde github.com)

Our personal feeling is that you are correct in that adding an updated field is outside of the scope of the pull request.

We'll review this after dinner, thanks for contributing :)

Our personal feeling is that you are correct in that adding an updated field is outside of the scope of the pull request. We'll review this after dinner, thanks for contributing :)
epsilon-phase (Migrado desde github.com) aprobado estos cambios hace 4 años
papey comentado hace 4 años (Migrado desde github.com)

Here is the issue related to update field for blog entries https://github.com/Plume-org/Plume/issues/722

Here is the issue related to update field for blog entries https://github.com/Plume-org/Plume/issues/722

Revisores

El Pull Request se ha fusionado como 23049b638c.

Paso 1:

Desde el repositorio de su proyecto, revisa una nueva rama y prueba los cambios.
git checkout -b fix/#673-date-id-rss master
git pull origin fix/#673-date-id-rss

Paso 2:

Combine los cambios y actualice en Forgejo.
git checkout master
git merge --no-ff fix/#673-date-id-rss
git push origin master
Inicie sesión para unirse a esta conversación.
No hay revisores
Sin Milestone
No asignados
1 participantes
Notificaciones
Fecha de vencimiento
La fecha de vencimiento es inválida o está fuera de rango. Por favor utilice el formato 'aaaa-mm-dd'.

Sin fecha de vencimiento.

Dependencias

No se han establecido dependencias.

Referencia: Plume/Plume#720
Cargando…
Aún no existe contenido.