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

Impossible to Generate SDK Code Due to Missing src/lib Folder After Commit #12eef67 #109

Open
aurimasniekis opened this issue Jan 27, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@aurimasniekis
Copy link

It seems that someone (commit 12eef67) decided to delete the entire src/lib folder. This is the folder that, you know, actually contains the essential code needed to generate the SDK. Without it, the specs here are about as useful as a chocolate teapot.

This raises a few questions:

  1. Was this deletion intentional? If so, are we supposed to manually reconstruct the folder from thin air? Or is there some secret magical replacement we’re all supposed to telepathically know about?
  2. If this was a mistake, why hasn’t it been reverted yet? It seems… unusual for a production repository of this caliber to have such a glaring oversight for this long.
  3. Is there any documented alternative process for code generation that doesn’t involve the now-missing src/lib folder? Because if there is, it’s certainly not where anyone can find it.

Steps to Reproduce:

  1. Clone the repository.
  2. Look for src/lib.
  3. Realize it’s missing and experience a moment of existential dread.

Expected Behavior:

The src/lib folder should exist, as it’s necessary for generating the SDK. Or at least there should be some explanation in the documentation about what we’re supposed to do without it.

Actual Behavior:

The folder is gone. It’s like someone just deleted the bridge while we were halfway across the river.

Suggested Actions:

  1. Either restore the src/lib folder or provide detailed instructions on the new process for code generation.
  2. If this was an intentional change, a heads-up in the documentation would have been nice preferably before the commit broke everything.

We’re all eagerly awaiting the resolution of this issue so we can get back to, you know, actually using the SDK.

Looking forward to seeing this resolved soon (hopefully before the next millennium). 😊

@aurimasniekis aurimasniekis added the bug Something isn't working label Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant