Late attachment of Downgraded plugin does not clean up the caches

I am trying to do something very simple and what I consider intuitive… I am trying to create a global state which is an array of objects, and then tap into it later, getting and setting that global state. Problem is I’m not able to get() the value of this state, let alone set() it.

I have this:

import { createState, useState } from '@hookstate/core'

interface KeyValues {
  [key: string]: string; //e.g. "Date": "7/5/2015"
}

interface KeyValuesByDoc {
  docName: string;
  docType: string;
  docID: string;
  keyValuePairs: KeyValues;
  interpretedKeys: KeyValues;
}

const getKeyValuePairsByDoc = (): KeyValuesByDoc[] => {
...
...
return docData 
}

export const globalDocData = createState(getKeyValuePairsByDoc())

...
...
...

// in a component, 
const docData = useState(globalDocData)

console.log(docData.get())
// => TypeError: docData.get is not a function

Now I understand that this isn’t necessarily the right way to access the state of an object… even following the docs, the example given doesn’t work:

const exampleObjectData = { a: 1, b: 2 }
const globalExampleObject = createState(exampleObjectData)

....
...
...

// in a component 
const exampleState = useState(globalExampleObject)
console.log(exampleState.keys)
// => Proxy{} 
// expected output: [a, b] per the docs

Really simple question… how can I ‘get’ the state value of an array of objects? Can I not just get it… do I have to map it first? Why isn’t it as simple as just doing .get() like for primitives?

I also tried the fix mentioned in this thread…

import { Downgraded } from '@hookstate/core'

// in a component
const exampleState = useState(globalExampleObject)
console.log(exampleState.attach(Downgraded).get())
// => TypeError: exampleState.attach is not a function

[meerkat-citronella]

Here is a code sandbox with the issue recreated. I wasn’t able to recreate what I’m seeing in my app in the sandbox.

I realized I was running v2.0.1… upgraded to v3.0.1. This didn’t solve the issues, but it prevent them from causing breaking errors. Here are screenshots from my app:

Creating the state:

Using the state in a component:

As you can see, the attach() and get() methods are no longer throwing errors, but they are still returning the proxy instead of the actual object.

[avkonst]

Fix released in 3.0.6