pedestal

simongray 2025-06-23T08:20:55.692939Z

is there a document somewhere that details how to migrate to 0.8 from 0.7? I’m getting a bunch of deprecation warnings now that I started using the beta.

simongray 2025-06-25T07:08:43.898259Z

@hlship Thanks. I'll take a look.

simongray 2025-06-24T07:10:22.347449Z

OK, but is there some example code using the new API? I have been using Pedestal for years, so the entire way to structure things and the functions are so ingrained that it’s hard for me to visualise how to structure things now. Do we still use service maps? Where do these connectors go? Stuff like that.

simongray 2025-06-24T07:11:32.528319Z

The API docs are a bit too granular for me 😅

hlship 2025-06-24T14:07:38.546139Z

All of the guides have been rewritten around the new APIs.

2025-06-23T08:55:22.251179Z

The long list of deprecations and things to be removed by 1.0 sort of implies that any Pedestal apps already written are toast and will need rewriting or porting to a stable platform.

hlship 2025-06-23T16:57:18.384809Z

I should work on that. To be honest, the majority of Pedestal hasn't been deprecated, as the core interceptor engine and interceptors haven't been deprecated. All that's really been deprecated is the startup code, so the work is to shift from using io.pedestal.http to io.pedestal.connector. An existing app moved to the connector should see few, if any, deprecation warnings.

hlship 2025-06-23T16:57:57.892089Z

Generally, the next step after a deprecation warning is to look in the API docs as the deprecated function will identify what to use instead.

hlship 2025-06-23T16:58:09.381969Z

I'm sure there are missed cases and such, please report them here or as a Pedestal issue.

hlship 2025-06-23T17:00:51.799889Z

Finally, 1.0 is easily 12 - 18 months away.

hlship 2025-06-23T17:01:43.229939Z

So I wouldn't call that "toast".

❤️ 2