nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc As an outsider looking at NDK for the first time, the events directory seems kind of all over the place... Ya'll got some plans to organize this a bit better?
no plans from my side. what are you finding confusing?
Create one directory for each of these .ts files, rename the file into index.ts and put it inside the directory.
That's the only way nostr:npub1zmc6qyqdfnllhnzzxr5wpepfpnzcf8q6m3jdveflmgruqvd3qa9sjv7f60 will be happy.
Sure, but not necessarily. Doing things multiple ways instead of one way does make a dk a bit harder to use because I have to go look at the repo to see which way when using it. I'm not saying I know anything. I'm stupid. So if there's a reason for the way it is, enlighten me and I'll be less stupid. You guys are the smart ones here.
Too many subdirectories make the code harder to browse.
Well... in the event dir, there's a nip but then in the kinds folder there's also a nip and other directories. idk maybe I just haven't looked through thoroughly enough but I guess that's what I'm getting at is deciphering the flow for adding thingd to the NDK is not straight forward.
Fair. There are some nips that define new kinds (usually on the kinds sub dir) and there are other nips that define behavior or events etc.
It definitely assumes quite a lot of knowledge of the nips.
