[very small] ensure lightdash generate keeps yaml copyright notice
See original GitHub issueDescription
lightdash generate
is very useful to generate information on fields we want to show on lightdash, saving the developer from writing lots of lines of code. One pain for myself is that this function removes any copyright information in the first line.
Example .yml
# Company Name, Inc. Proprietary and Confidential. Copyright 2022.
version: 2
models:
- name: test
columns:
- name: id
description: ""
meta:
dimension:
type: string
When running lightdash generate
this removes line 1, the copyright comment. This means that the .yml will fail our linting process.
What problem does this solve?
Described above
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Cannot dump no values with comments · Issue #196 - GitHub
So with another words, js-yaml always put value in quotes if you have any special ... [very small] ensure lightdash generate keeps yaml...
Read more >Autogenerate Lightdash-ready .yml files for your models
yml files, the Lightdash CLI will automatically generate and sync your schema.yml files. Inside your dbt project, open a terminal and run this...
Read more >Update your project connection | Documentation | Lightdash
1. Connect to a warehouse. We always recommend giving read-only permissions to Lightdash, that way you ensure than no data can be manipulated....
Read more >Formatting your fields | Documentation - Lightdash Docs
We've built a bunch of features to help you to format the fields in your dbt project so that the data in your...
Read more >Dimensions reference sheet | Documentation - Lightdash Docs
For a dimension to appear in Lightdash, you just need to declare it in your dbt model's YAML file. version: 2 models: -...
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 FreeTop 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
Top GitHub Comments
That’s annoying 😓 added to the backlog - hopefully should be an easy fix 🤞
thanks for the quick turnaround on this one!