Checking an Updated Tastic Schema

You can test how an updated Tastic Schema will behave before it's actually uploaded to Backstage. 

Please note, as this is a Developer test, this should only be done within your development systems. You'll have to add the Schema to Backstage if you want to add it to the Staging or Production environments.

Update to your Tastic Schema in a .json file as you normally would while making sure it's Backwards Compatible (see this article for more info)
Save the new version of your Tastic Schema as: $project/config/tasticSchemaOverwrites/$tasticName.json
Where $project is the name of your Project and $tasticName

is the name of the Tastic you're editing. Only .json files will be process in this folder so they must be in this format.

Your configuration will now override the already existing Tastic so you can now test the new Schema as you wish
Once you're happy with your new Tastic Schema, upload it to Backstage as usual
Delete the .json file from the tasticSchemaOverwrites folder

If you commit these files to Production, it will overwrite the existing Tastic so make sure it's working (and Backwards Compatible) if you do this or it could break things for your Frontend Managers or your users. Also be sure to delete the file (step 5) or this will be used over your Backstage version if it is committed.

Just to reiterate, that this can only be done for existing Tastic Schemas, you can't do this for a brand new Tastic. If you did want to test a new one, you would have to first upload a basic version of your Tastic (with no configurable options) to Backstage Production and then you can do this test.

‹ Back to Article List

Next Article ›

Tastic Field Handler

Still need help? Contact Us Contact Us