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 README for CLI v4 beta #26

Merged
merged 8 commits into from
Dec 20, 2024
Merged

Update README for CLI v4 beta #26

merged 8 commits into from
Dec 20, 2024

Conversation

jrodewig
Copy link
Contributor

@jrodewig jrodewig commented Dec 15, 2024

  • Updates the README for the CLI v4 beta.
  • Adds a .seed.sh file so users can add test data
  • Updates some .fql files used for test data

@jrodewig jrodewig changed the title Update README for CLI v4 Update README for CLI v4 beta Dec 15, 2024
@jrodewig jrodewig requested review from findgriffin and a team December 16, 2024 16:38
@jrodewig jrodewig marked this pull request as ready for review December 16, 2024 16:38
Copy link
Contributor

@findgriffin findgriffin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want, I can rejigger those test scripts, which are now referenced from .github/workflows and update this PR?

setup.sh Outdated
Comment on lines 1 to 7
fauna query --input seed/categories.fql --secret "$FAUNA_SECRET"
echo -e "\n\n"
fauna query --input seed/customers.fql --secret "$FAUNA_SECRET"
echo -e "\n\n"
fauna query --input seed/products.fql --secret "$FAUNA_SECRET"
echo -e "\n\n"
fauna query --input seed/orders.fql --secret "$FAUNA_SECRET"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You probably didn't see it, but I put a new file test/setup.sh that somewhat duplicates this file, I think we need to rename that file, or this file. Maybe we could rename this one seed.sh and put this script along with setup.sh and validate.sh in a directory called scripts?

Copy link
Contributor Author

@jrodewig jrodewig Dec 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I did the following:

  • Renamed this file to seed.sh and placed it in /scripts.
  • Moved /test/* files over to /scripts.
  • Updated references in test.yml
  • Deleted some redundant data in /seed/*.json files.

There's some additional work needed to update test.yml to the CLI v4 beta. Once that's done, we can just call seed.sh from setup.sh. However, that's a bit beyond the scope of this PR. I can tackle that in a separate PR if wanted.

Feel free to push changes to this PR/branch. Appreciate you taking a look!

@jrodewig jrodewig requested a review from findgriffin December 20, 2024 14:27
@findgriffin findgriffin merged commit 3fe95bb into main Dec 20, 2024
1 check passed
@jrodewig jrodewig deleted the update-cli-v4 branch December 20, 2024 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants