Project structure discussion

nas5w / semantic-validation

Semantic validation for javascript objects.

2 stars 1 forks source link

Project structure discussion #1

Open nas5w opened 5 years ago

nas5w commented 5 years ago

Moving this email discussion to a github issue, let's figure the following out:

What are the non code-related high level things the project needs? Docs, testing, CI, versioning, branding..? Maybe we can formalize this list in a github issue.
How we'll propose and delegate new features (I potentially envision that one of us would raise an issue on github, quick discussion of whether and how to integrate it, and then agree on who implements it)

:fire: :fire: :fire:

nas5w commented 5 years ago

One additional thought here: do we want to do a deep dive into whether there are good packages that do something similar? FWIW, I haven't seen anything, which means there's probably nothing that's widely used... but there could be. Would it even derail this project if we found something? If not, then I say we plow ahead with reckless disregard for whatever else is out there.

akuny commented 5 years ago

joi looks sort of close to what we're up to here: https://github.com/hapijs/joi

IMO it's worth moving forward regardless, but some digging into what sort of JSON validation packages exist and then considering what those packages don't do would be a good exercise

Delegation as proposed sounds good, as does drafting a list of high-level needs. I'd also like to start sketching out common JSON validation use cases as a means of understanding what the public API will look like.

nas5w commented 5 years ago

Joi does look quite similar! I agree some research is warranted to see if we can offer some kind of innovation. Any thoughts on a methodology to identify use cases?