kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/app/assets/javascripts/ide/components/repo_tabs.vue

28 lines
435 B
Vue
Raw Normal View History

Start on components
2017-07-24 12:15:41 -04:00
<script>
[WIP] Move multi-file editor store to Vuex
2017-10-26 06:14:31 -04:00
import { mapState } from 'vuex';
Refactored multi-file data structure This moves away from storing in a single array just to render the table. It now stores in a multi-dimensional array/object type where each entry in the array can have its own tree. This makes storing the data for future feature a little easier as there is only one way to store the data. Previously to insert a directory the code had to insert the directory & then the file at the right point in the array. Now the directory can be inserted anywhere & then a file can be quickly added into this directory. The rendering is still done with a single array, but this is handled through underscore. Underscore takes the array & then goes through each item to flatten it into one. It is done this way to save changing the markup away from table, keeping it as a table keeps it semantically correct.
2017-10-13 05:08:10 -04:00
import RepoTab from './repo_tab.vue';
Start on components
2017-07-24 12:15:41 -04:00
Refactored multi-file data structure This moves away from storing in a single array just to render the table. It now stores in a multi-dimensional array/object type where each entry in the array can have its own tree. This makes storing the data for future feature a little easier as there is only one way to store the data. Previously to insert a directory the code had to insert the directory & then the file at the right point in the array. Now the directory can be inserted anywhere & then a file can be quickly added into this directory. The rendering is still done with a single array, but this is handled through underscore. Underscore takes the array & then goes through each item to flatten it into one. It is done this way to save changing the markup away from table, keeping it as a table keeps it semantically correct.
2017-10-13 05:08:10 -04:00
export default {
components: {
'repo-tab': RepoTab,
[ci skip] eslint-fix
2017-08-01 09:41:24 -04:00
},
[WIP] Move multi-file editor store to Vuex
2017-10-26 06:14:31 -04:00
computed: {
...mapState([
'openFiles',
]),
Fixed bug when clicking file link causing user to navigate away Adds a test for flattenedFiles Changes the data method to not be an arrow method Various other review fixes
2017-10-17 06:03:12 -04:00
},
Refactored multi-file data structure This moves away from storing in a single array just to render the table. It now stores in a multi-dimensional array/object type where each entry in the array can have its own tree. This makes storing the data for future feature a little easier as there is only one way to store the data. Previously to insert a directory the code had to insert the directory & then the file at the right point in the array. Now the directory can be inserted anywhere & then a file can be quickly added into this directory. The rendering is still done with a single array, but this is handled through underscore. Underscore takes the array & then goes through each item to flatten it into one. It is done this way to save changing the markup away from table, keeping it as a table keeps it semantically correct.
2017-10-13 05:08:10 -04:00
};
Start on components
2017-07-24 12:15:41 -04:00
</script>
<template>
Refactored multi-file data structure This moves away from storing in a single array just to render the table. It now stores in a multi-dimensional array/object type where each entry in the array can have its own tree. This makes storing the data for future feature a little easier as there is only one way to store the data. Previously to insert a directory the code had to insert the directory & then the file at the right point in the array. Now the directory can be inserted anywhere & then a file can be quickly added into this directory. The rendering is still done with a single array, but this is handled through underscore. Underscore takes the array & then goes through each item to flatten it into one. It is done this way to save changing the markup away from table, keeping it as a table keeps it semantically correct.
2017-10-13 05:08:10 -04:00
<ul
Added IDE commit panel Closes #40041
2017-11-23 12:16:01 -05:00
class="multi-file-tabs list-unstyled append-bottom-0"
Refactored multi-file data structure This moves away from storing in a single array just to render the table. It now stores in a multi-dimensional array/object type where each entry in the array can have its own tree. This makes storing the data for future feature a little easier as there is only one way to store the data. Previously to insert a directory the code had to insert the directory & then the file at the right point in the array. Now the directory can be inserted anywhere & then a file can be quickly added into this directory. The rendering is still done with a single array, but this is handled through underscore. Underscore takes the array & then goes through each item to flatten it into one. It is done this way to save changing the markup away from table, keeping it as a table keeps it semantically correct.
2017-10-13 05:08:10 -04:00
>
<repo-tab
[WIP] Move multi-file editor store to Vuex
2017-10-26 06:14:31 -04:00
v-for="tab in openFiles"
Upgraded all vue libraries
2018-01-23 04:37:07 -05:00
:key="tab.key"
Refactored multi-file data structure This moves away from storing in a single array just to render the table. It now stores in a multi-dimensional array/object type where each entry in the array can have its own tree. This makes storing the data for future feature a little easier as there is only one way to store the data. Previously to insert a directory the code had to insert the directory & then the file at the right point in the array. Now the directory can be inserted anywhere & then a file can be quickly added into this directory. The rendering is still done with a single array, but this is handled through underscore. Underscore takes the array & then goes through each item to flatten it into one. It is done this way to save changing the markup away from table, keeping it as a table keeps it semantically correct.
2017-10-13 05:08:10 -04:00
:tab="tab"
/>
</ul>
Start on components
2017-07-24 12:15:41 -04:00
</template>
Copy permalink