You must log in or register to comment.
Will the new lemmy ui be ready for 1.0?
Yes we always release backend and frontend versions together.
Can’t give an ETA yet. I’ve got a few more back-end things to finish up, then @sleeplessone1917 and I will work on lemmy-ui.
Then I also gotta work on getting jerboa updated also. So much work and so few developers.
I can say I was there when Lemmy 1.0 released!
Will there be an overlap period where both APIs function?
Yes the current api v3 is also available in 1.0 alpha
Perfect, thank you.
Holy shit, it’s going gold!
Oh yes!
Really looking forward to SSO support!
💪
Does this mean you renamed just the DB columns, but not the API keys?
They’re all renamed, that PR just hasn’t been deployed to voyager.lemmy.ml yet.
Ah, good to know before I start developing. Can you let me know when we can start the development as I don’t want to use the API and then discover it’s missing more PRs?
I can’t say yet, as we’re still adding things. If you’re not using lemmy-js-client, then as long as your types are generated from it’s main branch directly, then you should be fine.
I’m not using the js-client. I’m updating pythorhead so I need to make sure the API is at the final version before I can match it. And to match it I need the patches to be in so I can read the doc, and/or import the swagger.
I will do what I can in advance, but to do the pre-development you asked for, we do need the final version up somewhere.
The updated spec should be at https://join-lemmy.org/api/main , and it gives you an option to download the
.jsonfileOr you can use the lemmy-js-client main branch, and run
pnpm tsoato generate aswagger.jsonfile.The final api version would probably be in 1.0-beta.0, which will still take a few months. But at this time you can already start to adapt for the major changes like combined endpoints, and give feedback if anything else in the api needs changing.
Oof, lots of work to do for everyone.
If anyone can figure out all the non-mentioned API changes and write them here it would be useful for people like me to avoid having to reverse engineer things
CORS is broken on voyager.lemmy.ml. Can you please fix it?
K I think it should be fixed now.
Awesome works!
Only thing I’ve noticed so far is the old v3 profile API response doesn’t have posts/comments attached
Yep I think we note that in the breaking changes post. We only serve the combined responses now.
wow! Huge, just when I am back to the saddle
Really excited for these changes; scheduled posts, donations, SSO, let’s goo
Nice
just passing by to congratulate you guys on the milestone!
Quick question mostly for @phiresky:
Are you targeting post tags for 1.0 or for later?Thx for the work.
