Skip to content

Instantly share code, notes, and snippets.

@Naoray

Naoray/addon-within-own-namespace.yaml

Last active April 17, 2020 11:54
Show Gist options
  • Save Naoray/91efb48fca1642800f5c7ddda652c454 to your computer and use it in GitHub Desktop.
Save Naoray/91efb48fca1642800f5c7ddda652c454 to your computer and use it in GitHub Desktop.
Download ZIP
Ideas on how to add addon's definition to blueprint
Raw
addon-within-own-namespace.yaml
models:
Post:
author_id: id:user
# other field definitions
Comment:
post_id: id
addons:
nova:
Post:
author: searchable
Comment:
post: searchable
Raw
another-idea.yaml
models:
Post:
author_id: id:user
# other field definitions
Comment:
post_id: id
# other field definitions
nova:
Post:
author: searchable
Comment:
post: searchable
Raw
draft.yaml
models:
Post:
author_id: id:user searchable
# other field definitions
Comment:
post_id: id searchable
# other field definitions
@Naoray
Copy link
Author

Naoray commented Apr 17, 2020

The easiest for the addon devs would be to simply merge their definitions with the original blueprint definitions like adding a searchable to the field definition draft.yaml. This would most likely cause a lot of confusion and probably errors from the blueprint:build command.

The other ideas are hopefully self-explanatory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment