Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2024-01-05

Channels

#pedestal
<
2024-01-05
>
hlship01:01:27

Having the code, documentation, and now build system all integrated together is chef_kiss .

hlship01:01:21

Short of making people use your APIs, there's nothing like writing the documentation and examples to identify problems.

👍 1
hlship01:01:38

Can't describe it succinctly or understandably? It's probably not right.

🎯 1
phill01:01:46

"Documentation-driven development" https://gist.github.com/zsup/9434452

ericstewart14:01:12

As someone who had tried Pedestal years ago and is looking at it again now, thank you for all the documentation work. I am finding it very helpful and appreciate the improvements.

➕ 2
gratitude 2
thanks3 1
hlship19:01:47

I think this is going to make people's lives a lot better: https://github.com/pedestal/pedestal/pull/796

🎉 2
hlship23:01:40

Numerous documentation updates today; but this is a biggie, I think: http://pedestal.io/pedestal/0.7/reference/libraries.html

🎉 2
nice 1
john-shaffer00:01:30

I had to do that to get the broken pipe changes, but there was an unresolveable conflict I ended up with this: io.pedestal/pedestal.jetty {:mvn/version "0.6.3" :override-deps {io.pedestal/pedestal.service {:git/url "" :git/sha "bd30d1cbc4447732d51ae989c0a331e8cfbfddcf"}}} I think your example works fine in the root deps.edn, but in my case pedestal is in a library deps.edn

hlship01:01:18

Yes, I was working quickly and should have noted use of :override-deps rather than ordinary :deps.

john-shaffer01:01:19

I guess I should use the same git/sha ref for pedestal.jetty as well

john-shaffer01:01:01

Loving the new docs btw

hlship01:01:32

I'm quite proud of what I've accomplished. Thanks!

hlship01:01:58

That could be more complete, more cohesive/consistent, etc. That just takes time.

hlship23:01:48

This describes how to bypass Clojars and get latest right from Git.

hlship23:01:33

It's great that using Antora and little bit of scripting, the version number in the documentation will always match the current version number. When we eventually release 0.7.0-alpha-1, that will be updated in all the examples and all the documentation as well.