Support for large schema files
See original GitHub issueI have a JSON schema generated for Ansible modules to simplify writing of Ansible roles:
"yaml.schemas": {
"/opt/ansible-schemas/": "ansible.json"
}
(you can find the file here https://raw.githubusercontent.com/shaded-enmity/ansible-schema-generator/master/examples/ansible.json and some example Ansible role here https://raw.githubusercontent.com/shaded-enmity/prototype/master/ansible_roles/docker/tasks/main.yml)
The problem is that the completion doesn’t really work properly and I’m seeing suggestions that are out of context - for example the state
key under yum
is not suggested at all.
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (7 by maintainers)
Top Results From Across the Web
Support for splitting Prisma schema into multiple files #2377
Prisma currently only supports one single Prisma Schema file. Developers want more flexibility for managing their Prisma Schema files.
Read more >Modularizing your GraphQL schema code
To organize your code, you'll want to split up your schema types and the associated resolvers into multiple files.
Read more >Organizing large schemas in GraphQL - Compiled Experience
A GraphQL service is made up for two parts, a schema and a collection of resolvers. The approaches for defining the schema will...
Read more >Specifying a schema | BigQuery - Google Cloud
Manually specifying a schema is supported when you load CSV and JSON (newline delimited) files. When you load Avro, Parquet, ORC, Firestore export...
Read more >How to use Prisma with multiple database schemas
Multiple database schema support is currently available with the ... refer to them as database schemas to distinguish them from Prisma's own schema...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@gorkem @languitar PTAL: Pending PR for SchemaStore with schemas for Ansible 2.0 through 2.5
@ssbarnea Please open issues/enhancements in https://github.com/shaded-enmity/ansible-schema-generator/ — the current schemas are meant to be used with
tasks/*
only, however it should be possible to make them work in a broader context of tasks directly “embedded” into roles/playbooks. I’ll take a look what I can do aboutset_facts
in the meantime.Thanks!