You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the Field Plugin Sandbox only displays the content and the data.
I would suggest for a possibility to enter data.
Not a problem, but would help to develop plugins, that access content of the current story.
Describe the solution you'd like
The complete data structure (incl. content) should be editable and provided to the field plugin as storyblok would do it in real life.
Describe alternatives you've considered
Currently the data will be taken from an .env.local file and "simulated" that this data comes from stroyblok
The text was updated successfully, but these errors were encountered:
If I understand your request correctly, do you want to have an actual (or simulated) payload of whole story within the Sandbox? I'm curious to hear your example / experience on how it could make difference in your workflow :)
Initially it would be enough to have just a simulated payload that can be entered (or pasted in) manually.
It's used for manual testing the behavior of the plugin entering the first time (with no plugin specific data set) and the further times (when the user has changed data in the plugin)
To have an actual payload, that can be selected would make life easier - sure ;-)
Is your feature request related to a problem? Please describe.
Currently the Field Plugin Sandbox only displays the content and the data.
I would suggest for a possibility to enter data.
Not a problem, but would help to develop plugins, that access content of the current story.
Describe the solution you'd like
The complete data structure (incl. content) should be editable and provided to the field plugin as storyblok would do it in real life.
Describe alternatives you've considered
Currently the data will be taken from an .env.local file and "simulated" that this data comes from stroyblok
The text was updated successfully, but these errors were encountered: