Weird / destructive behaviour using mapActions service find between components

I’m having a weird behaviour using find, this is how I’m using it:

I’m using feather-vuex 0.4.2, I also tried 0.3.1 and I get the same result.

First component

On the first component I do a find without a query, it returns all the results and store them on vuex.

methods: {
	...mapActions('profiles', { findProfiles: 'find' }),

	fetch() {
		this.findProfiles({})
	},
},

created() {
	this.fetch()
},

Screenshot of Vuex state after find:

Second component

Now I do a get and after it the results fetched with the find are still in the store. Everything is fine here.

methods: {
	...mapActions('profiles', { getProfile: 'get' }),

	fetch() {
		this.getProfile(this.user.profile)
	},
},

created() {
	this.fetch()
},

Third component

Now I do other find but with a custom query, I just want to find an element, the query works fine but it destroy the results of the first find 😦

methods: {
	...mapActions('profiles', { findProfile: 'find' }),

	fetch() {
		this.findProfile({
			query: { slug: this.$route.params.slug },
		})
	},
},

created() {
	this.fetch()
},

Is this a bug or the expected behaviour? I’m missing something?

[marshallswain]

Thanks for reporting back. It will take me some time to figure out a solution.

[dortamiguel]

I tried again version 0.3.0 and 0.3.1 and now all the data persists 😄

Probably I didn’t removed correctly the 0.4.2.

I still have to learn how to use breakpoints…