-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(contribs): publish contributions in the new format #1025
Conversation
# Conflicts: # targets/alert-cli/package.json # targets/ingester/src/lib/fetchContributions/__tests__/expected.json # yarn.lock
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: [email protected], [email protected], [email protected], [email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
top le refacto ! le code est beaucoup plus simple
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Top !
@@ -1,6 +1,7 @@ | |||
import type { | |||
AgreementDoc, | |||
ContributionCompleteDoc, | |||
ContributionGenericDoc, | |||
ContributionWithCCDoc, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ContributionWithCCDoc, | |
ContributionWithAgreementDoc, |
Pour une meilleur lecture et homogénéisation des termes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Après si on a générique, on peut utiliser le terme Personnalisé que le métier utilise pas mal -> ContributionCustomizedDoc
ou j'aurais mis plutôt CustomizedContributionDoc
et GenericContributionDoc
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah oui les 2 sont bien
description: string; | ||
answers: CCMultipleAnswers; | ||
answer: Answer; | ||
agreementsWithAnswer: string[]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Peut-être customizedAgreements
pour être raccord ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pour le coup c'est bizarre non ? Pour le métier "personnalisé" c'est quand on a une CC.
La je liste juste les CC qui ont une réponse pour cette contrib
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ou alors supportedAgreements
pour être raccord avec nos outils ?
shared/types/index.ts
Outdated
title: string; | ||
url?: string; | ||
}; | ||
|
||
export type BaseRef = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Je trouve BaseRef pas adapté. Ce sont nos contenus et ce ne sont pas des références mais des contenus liés. On pourrait le renommer CdtnRelatedContent
?
text: string; | ||
content?: string | FicheServicePublicDoc; | ||
}; | ||
type AnswerWithCC = Answer & { idcc: string; shortName: string }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Idem ici, on peut nommer CustomizedAnswer
if (!genericAnswer) { | ||
return null; | ||
throw new Error("No generic answer found"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ça pourrait être bien d'ajouter la question liée pour le debug.
is_searchable: false, | ||
slug: slugify(`${parseInt(idcc, 10)}-${title}`), | ||
source: SOURCES.CONTRIBUTIONS, | ||
text: `${idcc} ${title}`, // actuellement c'est comme ça mais si la CC a son propre contenu est-ce que ça ne devrait pas être dans text aussi ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A voir après l'intervention de rémi si ce champ sera encore nécessaire.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok je vire le comment faudra qu'on retravail ça
# Conflicts: # shared/types/package.json # yarn.lock
…tatuts dans les contribs (#1070)
description: string; | ||
answers: CCMultipleAnswers; | ||
answer: Answer; | ||
agreementsWithAnswer: string[]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ou alors supportedAgreements
pour être raccord avec nos outils ?
* fix: v1 * fix: delete com * fix: restore * show error * fix: modif --------- Co-authored-by: carolineBda <[email protected]>
* fix: merge * fix: merge * fix: build * fix: build * fix: build * fix: url * fix: types * fix: expected by snapshot * fix: test * fix: test * fix: test --------- Co-authored-by: carolineBda <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Fix https://github.com/orgs/SocialGouv/projects/95/views/1?pane=issue&itemId=36609333