"editOnly" option not working with global contexts

Developer Support
1

Hello! I have a quick question about global contexts. I’ve been trying to set one up with a prop that is only meant to be used by the studio using the editOnly option. However, when I use the prop in the studio and give it a value I can still see the code being generated if when I supply the editOnly option. Is this option for props not supported when combining with global contexts?

2

Registering the code component:

  PLASMIC.registerGlobalContext(ApiGlobalContext, {
    name: 'ApiGlobalContext',
    // ...removed for brevity
    props: {
      apiKey: {
        type: 'string',
        editOnly: true,
      },
    },
  });

I went in and set the context prop to a test value this_is_a_test

I went to my local setup using the headless API and still saw this in my page props for Next.js

\"apiKey\" in apiGlobalContextProps ? apiGlobalContextProps.apiKey : \"this_is_a_test\"\n
3

Hey @carefree_muskox. I’ll be investigating this issue. Thanks for the report

4

No worries happy to help!

5

This indeed looks like a bug. It should be fixed by the end of the day.

6

You should be able to sync it now and it shouldn’t use the value from Studio

7

Thank you so much for the quick turnaround! I can see the void 0 now being injected instead of the string value set in the studio