feature/projects-all-the-way-down #3323

Merged
konrad merged 123 commits from feature/projects-all-the-way-down into main 2023-05-30 10:09:40 +00:00
Showing only changes of commit be1f1d94c9 - Show all commits

View File

@ -72,7 +72,7 @@
</template>
<script lang="ts" setup>
import {ref, computed, watch, onActivated} from 'vue'
import {ref, computed, watch} from 'vue'
import draggable from 'zhyswan-vuedraggable'
import type {SortableEvent} from 'sortablejs'
@ -106,13 +106,12 @@ const currentProject = computed(() => baseStore.currentProject)
// TODO: child projects
const availableProjects = ref<IProject[]>([])
watch(

Really unsure here: Since we do map data directly from the store I'm unsure if we should emit and update the store. Because an emit will change data in the parent. An update from the store will probably as well.

Really unsure here: Since we do map data directly from the store I'm unsure if we should emit _and_ update the store. Because an emit will change data in the parent. An update from the store will probably as well.

It looks like it works fine without the emit. We're always binding with :modelValue instead of v-model anyway…

It looks like it works fine without the emit. We're always binding with `:modelValue` instead of `v-model` anyway…
props.projects,
() => props.projects,
projects => {
availableProjects.value = projects
},
{immediate: true},
dpschen marked this conversation as resolved Outdated

What consequence has this?

What consequence has this?

This now works, it didn't in an earlier version. I've removed the comment.

This now works, it didn't in an earlier version. I've removed the comment.
)
dpschen marked this conversation as resolved Outdated

What exactly needs to be done for child projects?

What exactly needs to be done for child projects?

That was an old comment, I've removed it

That was an old comment, I've removed it
onActivated(() => availableProjects.value = props.projects)
const projectUpdating = ref<{ [id: IProject['id']]: boolean }>({})