Skip to content

Conversation

@BlaineHeffron
Copy link
Contributor

Addresses stellar/stellar-cli#1438

Adds cookbook entries for:

  • A lifecycle of a contract (requested by the community)
  • Payment for XLM, classic asset, soroban assets

We cannot yet do the following because the commands are not available on the CLI:

@BlaineHeffron BlaineHeffron changed the title Add some requested doc cookbook entries Add some requested CLI cookbook entries Jul 31, 2024
@stellar-jenkins
Copy link

@gre3n3yes34

This comment was marked as off-topic.

@stellar-jenkins
Copy link

@ifropc
Copy link
Contributor

ifropc commented Aug 1, 2024

LGTM, just added a couple of small comments

@janewang
Copy link
Contributor

janewang commented Aug 6, 2024

@BlaineHeffron Ideally this could be in a single markdown file called cookbooks.mdx, with different paths for each recipe.

@janewang
Copy link
Contributor

janewang commented Aug 6, 2024

@BlaineHeffron I was thinking that this Cookbook.mdx could be added to the CLI repo next to the FULL_HELP_DOCS.md and we could copy it over the docs, similar to the CLI Manual is copied over: #755

@BlaineHeffron
Copy link
Contributor Author

@janewang Makes sense, I'll work on getting that set up.

@stellar-jenkins
Copy link

2 similar comments
@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

@BlaineHeffron
Copy link
Contributor Author

@janewang I opened a draft PR for a Cookbook.md file. stellar/stellar-cli#1541 I also added to the script an entry to copy over this Cookbook.md file to stellar-cli-cookbook.mdx alongside the stellar-cli.mdx file. I also added a link to it in the docs. I am wondering if you would like to copy all the existing stellar-cli guides that are currently here? https://developers.stellar.org/docs/build/guides/cli

@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

1 similar comment
@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

@janewang
Copy link
Contributor

Hey @BlaineHeffron The other file that's being copied over is this file: https://github.com/stellar/stellar-cli/blob/main/FULL_HELP_DOCS.md. I think we only need these two files to be copied.

@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

@BlaineHeffron
Copy link
Contributor Author

This PR can only be merged after stellar/stellar-cli#1541 is merged. In that PR I moved the guide mdx files to the CLI repo in a new /docs directory. In this PR I altered the script to copy over the mdx files from the /docs directory.

@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

@stellar-jenkins
Copy link

1 similar comment
@stellar-jenkins
Copy link

@janewang
Copy link
Contributor

janewang commented Sep 9, 2024

You can run yarn check:mdx to fix the markdown linting error

@BlaineHeffron
Copy link
Contributor Author

The problem is that I needed to add the yarn stellar-cli:build command to the git actions so that markdown files that link to the CLI cookbook entries wouldn't error during build. This means that the CLI docs markdown file gets linted and apparently it is producing warnings. This is the auto generated docs file from the CLI. Either we would have to fix the markdown formatting errors from the generated document or we just add stub files for all of the CLI cookbook entries and don't actually run yarn stellar-cli:build in the git actions.

@stellar-jenkins
Copy link

Something went wrong with PR preview build please check

@stellar-jenkins
Copy link

@fnando fnando merged commit 7bc7a74 into stellar:main Sep 10, 2024
janewang pushed a commit that referenced this pull request Sep 12, 2024
@ElliotFriend
Copy link
Contributor

@BlaineHeffron @janewang

Hi, friends!!

Sorry, i'm late to the party here, had a couple hectic weeks. Can I get a little more context about what brought this change about? I think I've picked up on reasonably on what is taking place in this change, but I'm a little unclear about the why. Is there a particular reason having these cookbook guides live alongside the CLI codebase is better off than having them live in the docs?

One of the reasons I'm asking is: now we're seeing the same broken link error Blaine mentioned in this comment if we're just using yarn start to preview locally while editing.

Thanks!

@briwylde08
Copy link
Contributor

briwylde08 commented Sep 16, 2024

Redacted.

@janewang
Copy link
Contributor

janewang commented Sep 17, 2024

There is a test that runs through the commands to make sure that they are valid on the CLI side. That test could only reasonably live in the CLI repo. That's why Blaine created the file on the CLI side and copied over to the docs.

Can someone point me to the broken links on the docs side? I heard it was mentioned but didn't see the links.

@ElliotFriend
Copy link
Contributor

@janewang you can see some of the fixes Bri was needing in some of the changed files in pr #982

@janewang
Copy link
Contributor

Thank you @briwylde08!

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.

8 participants