What is the expected visibility of associationIdKeys and associationKeys

Bug or question

I have a custom serializer which makes use of associationIdKeys and associationKeys to map the id attribute found in attrs back to the name of the key which is used to access the associated model. This was broken when these properties were changed to Set instead of Array instances (https://github.com/miragejs/miragejs/pull/151), which is fine, but it makes me wonder if our custom serializer should not be using those fields (they are not prefixed with underscore, but they are also not explicitly documented). Is there a better way to achieve what we are doing. For a very basic example of the type of thing we were doing, consider this snippet:

const customSerializedResult = Object.keys(modelInstance.attrs).reduce((result, currKey) => {
  if (modelInstance.associationIdKeys.includes(currKey)) {
    // ... get associationKey and retrieve nested model to serialize it
  } 
  
  // ... handle top level property
});

Is there a different or better way to be doing this?

[jackson-dean]

@samselikoff Haven’t had a chance to upgrade and check it yet, but it looks like it should work fine. Thanks so much!!

[samselikoff]

Released in v0.1.35, let me know if it works for you!

https://github.com/miragejs/miragejs/releases/tag/v0.1.35