Inability to check if the current entry pass all validations

[HQ063]

I think it will be really useful to be able to call sdk.entry.isValid() or something among that, to see if the current entry being edited pass al validations, the same way it's used on the publish button for enable/disabled state. I tried to find an alternative way by traversing through all fields on the entry an callinggetSchemaErrors on each of them, but that method is also not available through sdk.entry.fields[fieldName], so I can't call it on all fields. I'm building a sidebar app and I need to be able to check if the entry is valid, and even better if I can get all the validation errors.

[jjolton-contentful]

Hey Gonzalo Muñoz (@HQ063), I dropped you a message via a support channel, but wanted to duplicate my reply here as well.

I can totally see the value you propose in enhancing the app sdk's ability to determine if the current entry is wholly valid, and I've created a ticket to track the effort to determine the feasibility of exposing the getSchemaErrors method outside of the field sdk in order to better support the type of pattern you are referencing. I can't make any guarantees around timing of a change in that area, so I will go ahead and provide a workaround you can use immediately.

One of the most maintainable paths I see available today is to:

1. Add a tiny field-location version of your app to every field that matters.
2. In that field app, register sdk.field.onSchemaErrorsChanged and broadcast the current error array to your sidebar app by writing the state into a hidden field on your entry.
3. In the sidebar app, react to updates on that hidden field and use them to derive an “entry valid / invalid” state plus a combined list of errors.

It’s admittedly more plumbing than a single sdk.entry.isValid() call would be, but it’s an approach fully supported by the current App SDK surface.

[HQ063]

Thanks Jared Jolton (@jjolton-contentful) ,

follow up question on your approach:
For the "Add a tiny field-location version of your app to every field that matters.", would I need to set each field editor to my custom app, and then implement the actual editor on the app using the proper contentful-field-editors component myself? or is there a way to add the field-location app to the fields without having to change the field editor?