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

Add tooling in support of auto-update of code excerpts in docs #1635

Open
2 of 4 tasks
Tracked by #4082 ...
chalin opened this issue Aug 19, 2022 · 11 comments
Open
2 of 4 tasks
Tracked by #4082 ...

Add tooling in support of auto-update of code excerpts in docs #1635

chalin opened this issue Aug 19, 2022 · 11 comments
Assignees
Labels
CI/infra CI & infrastructure e1-hours Effort: < 8 hrs e3-weeks Effort: < 4 weeks p2-medium
Milestone

Comments

@chalin
Copy link
Contributor

chalin commented Aug 19, 2022

@svrnm - I remember you mentioning this somewhere, but I can't find the reference. Anyhow, I'm creating this issue to track progress on this work. /cc @cartermp

At the start of the year I introduced a simple verbatim code-copy shortcode, but what I have in mind would be more flexible.

Tooling use:

@chalin chalin added CI/infra CI & infrastructure e1-hours Effort: < 8 hrs p2-medium labels Aug 19, 2022
@svrnm
Copy link
Member

svrnm commented Aug 21, 2022

we discussed that on slack and/or the comms call a few months back, but I can't find it either.

Curious to see & discuss what you have in mind

@ekquasar
Copy link
Contributor

ekquasar commented Dec 4, 2023

There's the issue of keeping the code snippets in the docs updated to reflect working example code - and that is the topic of this issue, iiuc? But then there's the issue of keeping the example code tested. Is that also the subject of this issue?

@svrnm
Copy link
Member

svrnm commented Dec 5, 2023

We discussed this during yesterday's SIG meeting. @chalin will provide a proposal following some best practices other projects have implemented today already. For testing the go/example/dice and the go getting started will be used (cc @pellared, who has contributed both)

@ekquasar the PR may or may not answer your question around keeping things in sync, so let's wait for what @chalin's prototype will look like, early next year.

@zeitlinger
Copy link
Member

I'm in the process of adding more snippets, so this feature would be great.

See #4642

@svrnm
Copy link
Member

svrnm commented Jun 13, 2024

@zeitlinger we have tooling place, see #3948 and some of the Go Docs related to that, it's still under observation, but you can take a look and see if you can make use of it for java as well

@zeitlinger
Copy link
Member

why are the go samples not up-to-date then?

@svrnm
Copy link
Member

svrnm commented Jun 13, 2024

why are the go samples not up-to-date then?

they aren't? I guess because it is still a manual process to update them (cc @chalin)

@chalin
Copy link
Contributor Author

chalin commented Jun 13, 2024

Yes, given that this is still in development (and I'm hoping to bring in simpler tooling as soon as I have time to devote to this), the process is still manual.

@chalin
Copy link
Contributor Author

chalin commented Jun 13, 2024

Let me refresh those code excerpts now.

@svrnm
Copy link
Member

svrnm commented Jun 13, 2024

Let me refresh those code excerpts now.

#4678 I gave it a try 🙈 , since some of the code has been put into a separate file this is not only an update but also needs some textual changes

@chalin
Copy link
Contributor Author

chalin commented Jun 13, 2024

Thanks @svrnm. I'll let you handle it from here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/infra CI & infrastructure e1-hours Effort: < 8 hrs e3-weeks Effort: < 4 weeks p2-medium
Projects
Status: No status
Development

No branches or pull requests

4 participants