Initial release
4kimov opened this issue ยท 6 comments
Hey @laserpants, thanks for getting this codebase going! I'm trying to get this out of the door, so have a few questions:
- I've noticed some tests are not 1:1 with the spec. My Haskell knowledge is limited, is there any way to get them to cover the same scenarios?
- I've added a basic README. Think you could help me fill in the examples?
- Would you like to publish the package?
Anything else we're missing? If not, I can update the site whenever this is good to go!
Edit: 4. Is there a way to setup Github Actions for auto-testing? (so the badge shows tests are passing)
Hi @4kimov,
Thanks for checking in. There is still a bit of work to be done here. I was initially pushing the code to a temporary repository under my own account, but I decided to move it here once access was enabled, even though it is not quite ready. Not sure if that was the idea? ๐ค Otherwise I could move the code back to a less visible place, or push everything on a dev
branch in the meantime. What do you think, please? A preliminary timeline is to get this ready for more serious testing sometime this coming week.
Approximate progress bar:
[==============================> ]
- The tests are just sanity checks as this point, while still implementing the core encoding/decoding logic (decoding is mostly done). Certainly these must be replaced/complemented with the official tests.
- I suggest that this will follow after verifying that the official tests pass.
- Same as for previous item.
- I will look into this as well.
- Finish implementation of encoding
- Clean up/finalize API and project structure
- Add "official" tests
- Publish (on Hackage)
- Set up GitHub actions (CI)
- Update README file
- Comment code/API docs
- Release party in the Bahamas? โฑ๏ธ ๐
Hi @laserpants,
Great, thank you for the quick reply. I think at this point it's absolutely fine to keep going with the main
branch, it's a brand new repo. Later once people start using it, we can be more detailed about it and create extra branches as needed :)
Everything you're doing is great! Keep it up & let me know how I can help ๐
Just FYI: I adjusted the spec to match Microsoft's a bit better, so pushed an update to this repo as well.
@laserpants I think your docs are excellent. They're so full of information & even have a gif. Well done ๐
I've updated the website @ https://sqids.org/haskell. I don't see anything else to update for this repo (I also see you've gotten the tests to match the spec, which is great). Thank you for doing all of this!
For now looks like this repo is set. The next approximate steps are:
- For me to give Js + Rust + Go a bit of a push
- See if the org can get a few more popular languages going (doesn't have to be all 40 of them)
- A few days/weeks from now start redirecting (for example from https://hashids.org/haskell/ to https://sqids.org/haskell?hashids)
๐