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

📖 Update CaDeT user guidance post 1.8.x upgrade #4929

Closed
3 tasks
jhpyke opened this issue Aug 8, 2024 · 2 comments
Closed
3 tasks

📖 Update CaDeT user guidance post 1.8.x upgrade #4929

jhpyke opened this issue Aug 8, 2024 · 2 comments

Comments

@jhpyke
Copy link
Contributor

jhpyke commented Aug 8, 2024

User Story

As a user of CaDeT
I need to have up-to-date documentation
So that I can use the tool effectively without hitting avoidable errors.

Value / Purpose

With the recent DBT upgrade, we've added a bunch of new functionality. We've also deprecated the tests argument in favour of data_tests due to changes in DBT core functions. As such, the documentation needs a read through, and a check to see if it's still up to date with current state of the AP. It would also be worth writing a setup guide for VS Code, but this may be worth spinning out as a separate ticket (TBD in Refinement)

Useful Contacts

@jhpyke

User Types

No response

Hypothesis

If we... update our docs
Then... users will be better able to use our product

Proposal

Work through our current docs, and where the reality is no longer aligned with the docs, the docs should be updated to reflect the new methods under DBT 1.8.x

Additional Information

No response

Definition of Done

  • Documentation has been written / updated
  • VS Code specific setup has been written
  • Another team member has reviewed
Copy link
Contributor

github-actions bot commented Oct 8, 2024

This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open.

@github-actions github-actions bot added the stale label Oct 8, 2024
Copy link
Contributor

This issue is being closed because it has been open for a further 7 days with no activity. If this is still a valid issue, please reopen it, Thank you!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 15, 2024
@github-project-automation github-project-automation bot moved this from 👀 TODO to 🎉 Done in Analytical Platform Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

1 participant