Skip to content
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

Feature/page projets #18

Merged
merged 26 commits into from
Oct 14, 2024
Merged

Feature/page projets #18

merged 26 commits into from
Oct 14, 2024

Conversation

plduthoit
Copy link
Contributor

Contains :

  • Project list page + filters + order

Components :

  • Map
  • Modal
  • ChipGroup
  • Chip
  • Card (modified)

Layout :

  • Light header

@plduthoit plduthoit requested a review from 0live October 9, 2024 07:36
administrative_scope_3:
name: Départemental
administrative_scope_4:
name: Communal
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

je l'ai récupéré de ta branche mais dans l'idée plutot le gérer en enum.

Copy link
Contributor

@0live 0live left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Belle branche :)
J'ai quelques remarques, mais l'essentiel est surtout sur la façon dont on articule la carte et le reste de l'application. On pourra en parler directement, ça sera plus simple pour se mettre d'accord

@@ -76,13 +95,15 @@ class Project
private ?string $website = null;

#[ORM\Column(length: 255, nullable: true)]
#[Groups([self::PROJECT_READ_ALL])]
private ?string $logo = null;

/**
* @var Collection<int, Actor>
*/
#[ORM\JoinTable(name: 'financed_projects_actors')]
#[ORM\ManyToMany(targetEntity: Actor::class)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Il va falloir qu'on voit avec Maelle, mais je ne suis pas sur qu'il s'agira d'acteurs au sens de la plateforme ici, probablement qu'il s'agira d'une chaine de caractères. A vérifier

@@ -91,10 +112,12 @@ class Project

#[ORM\JoinTable(name: 'contracted_projects_actors')]
#[ORM\ManyToMany(targetEntity: Actor::class)]
#[Groups([self::PROJECT_READ_ALL])]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Même chose ici

@@ -12,10 +12,24 @@
height: 100vh;
}

:root {
--dim-container-w: 70rem;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Est ce qu'on ne stockerait pas toutes les variables à un seul endroit?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A réutiliser dans la fiche acteur, j'ai fait ça en css.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. On peut d'abord merger la tienne et je réadapterais en prenant ta Chip et ma ChipList.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Je pense que c'est mieux de mettre la logique de gestion de la map dans une classe hors du composant. Surtout qu'on va avoir plusieurs cartes qui vont partager des fonctionnalités. On peut mettre ça dans un map store et utiliser des services qui fourniront les différentes options.

@@ -1,4 +1,4 @@
export interface Thematic {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pareil, on peut utiliser l'interface SymfonyRelation

@@ -14,9 +14,21 @@ export const useApplicationStore = defineStore(StoresList.APPLICATION, () => {
const activeDialog: Ref<DialogKey|null> = ref(null)
const showEditContentDialog = ref(false)
const route = useRoute();
const isProjectMapFullWidth = ref(false)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Je le mettrais plus dans le store des projets ça

@@ -14,9 +14,21 @@ export const useApplicationStore = defineStore(StoresList.APPLICATION, () => {
const activeDialog: Ref<DialogKey|null> = ref(null)
const showEditContentDialog = ref(false)
const route = useRoute();
const isProjectMapFullWidth = ref(false)
const triggerZoomReset = ref(false)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Et ça dans le store de la map

vue/src/stores/applicationStore.ts Outdated Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Il faudra plugger la partie acteur dessus.

@plduthoit plduthoit merged commit d88c363 into main Oct 14, 2024
1 check passed
@plduthoit plduthoit deleted the feature/page-projets branch October 14, 2024 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants