Added docs/cloud toggle on the first few steps in build-your-first-mo… #878
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To follow up on this. The package-lock is restructured for me every time I run npm-install. It looks like it only restructures the file, while the dependencies still have the same version and the site behaves the same. So I don't see this as an issue. |
|
Looks great ✅ thank you for fixing this so quickly ✨ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description & motivation
See this Slack convo for context.
TL;DR: I added Cloud/Core toggle functionality to the first few steps of the process explained on
/tutorial/build-your-first-modelswhere previously, it was formatted with just Markdown headers.Pre-release docs
Is this change related to an unreleased version of dbt?
next<Changelog>[New/Changed] in v0.x.0</Changelog>current@JKarlavige I just want to call out that when I ran
npm installinsidewebsite, it updated thepackage-lock.jsonand it's going to be committed in this PR. I think it should be fine, but let me know if not!