Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/157 improve playbook execution speed by embedding the json schemas #199

Conversation

MaartendeKruijf
Copy link
Collaborator

@MaartendeKruijf MaartendeKruijf added enhancement New feature or request cacao OASIS cacao model related issue labels Aug 2, 2024
@MaartendeKruijf MaartendeKruijf self-assigned this Aug 2, 2024
@MaartendeKruijf MaartendeKruijf linked an issue Aug 2, 2024 that may be closed by this pull request
@MaartendeKruijf MaartendeKruijf merged commit 06f59c8 into development Aug 2, 2024
9 checks passed
@MaartendeKruijf MaartendeKruijf deleted the feature/157-improve-playbook-execution-speed-by-embedding-the-json-schemas branch August 2, 2024 08:41
Copy link
Collaborator

@lucamrgs lucamrgs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great to have this in the end! But I think it would be nice to have an option to re-build the local schemas from the remote repository, shall they change.

sch, err = compiler.Compile(oca_cacao_schemas)
if err != nil {
return err
schemaUrl := utils.GetEnv("VALIDATION_SCHEMA_URL", "")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we handle this logic so that we can automatically re-build the local schemas if they change?

if schemaUrl != "" {
return validateWithRemoteSchema(rawJson, schemaUrl)
} else {
return validateWithLocalSchema(rawJson)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we perhaps also have an option "build local schemas", invoked once when building the code, which populates the schemas according to the latest version? Or something along those lines?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cacao OASIS cacao model related issue enhancement New feature or request
Projects
None yet
3 participants