Fix RSS issues #720

Fusionnée
papey a fusionné 2 révision(s) à partir de fix/#673-date-id-rss vers master il y a 4 ans
papey a commenté il y a 4 ans (Migré de 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] a commenté il y a 4 ans (Migré de 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 a commenté il y a 4 ans (Migré de 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 (Migré de github.com) ces changements ont été approuvés il y a 4 ans
papey a commenté il y a 4 ans (Migré de 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

Relecteurs

La demande d'ajout a été fusionnée en 23049b638c.
Vous pouvez également voir les instructions en ligne de commande.

Étape 1:

Depuis le dépôt de votre projet, sélectionnez une nouvelle branche et testez les modifications.
git checkout -b fix/#673-date-id-rss master
git pull origin fix/#673-date-id-rss

Étape 2:

Fusionner les modifications et mettre à jour sur Forgejo.
git checkout master
git merge --no-ff fix/#673-date-id-rss
git push origin master
Connectez-vous pour rejoindre cette conversation.
Aucune évaluation
Aucun jalon
Pas d'assignataires
1 participants
Notifications
Échéance
La date d’échéance est invalide ou hors plage. Veuillez utiliser le format 'aaaa-mm-dd'.

Aucune échéance n'a été définie.

Dépendances

No dependencies set.

Reference: Plume/Plume#720
Chargement…
Il n'existe pas encore de contenu.