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

Provide a global strict option #45

Closed
danwkennedy opened this issue Aug 24, 2016 · 7 comments
Closed

Provide a global strict option #45

danwkennedy opened this issue Aug 24, 2016 · 7 comments
Assignees

Comments

@danwkennedy
Copy link

Instead of requiring each object set it's strict option, it'd be handy to just have a global type strict option. Most of the time, if I want one of my object rules to be strict, I want them all to be strict.

@Atinux Atinux added this to the Version 2.0 milestone Oct 28, 2016
@github-actions
Copy link

github-actions bot commented Apr 8, 2021

This issue is stale because it has had no activity for 60 days. It will be closed after 14 more days of no activity.

@github-actions github-actions bot added the Stale label Apr 8, 2021
@mattwelke
Copy link
Collaborator

@danwkennedy Do you think this feature would still be useful for you?

@danwkennedy
Copy link
Author

@mattwelke I believe it'd still be useful, however, I've since left the company that uses this package. Thank you for following up though! It's good to see this project getting some love :)

@mattwelke
Copy link
Collaborator

mattwelke commented Apr 8, 2021

Thanks for responding. "Love" is a strong word. :P It's an old library from before the new JSON Schema standards. But I've agreed to maintain it. We're still using it in production.

I'll close this, and people can reopen it if there's a need for the feature.

@Yash-Singh1
Copy link
Collaborator

I think this could be a useful option because it could prevent me from writing strict: true, every time.

@Yash-Singh1 Yash-Singh1 reopened this Apr 27, 2021
@Yash-Singh1 Yash-Singh1 removed the Stale label Apr 27, 2021
@Yash-Singh1 Yash-Singh1 self-assigned this Apr 27, 2021
@Yash-Singh1 Yash-Singh1 removed this from the Version 2.0 milestone Apr 27, 2021
@github-actions
Copy link

This issue is stale because it has had no activity for 60 days. It will be closed after 14 more days of no activity.

@github-actions github-actions bot added the Stale label Jun 27, 2021
@mattwelke mattwelke removed the Stale label Jun 27, 2021
@mattwelke
Copy link
Collaborator

I think this could be a useful option because it could prevent me from writing strict: true, every time.

We're going to move forward with a maintenance only approach for this library. We'll look for "would", not "could". If someone currently using it has a specific use case for a desired feature, we'd take it on. But we wouldn't add features for the sake of trying to grow the userbase, which isn't a goal right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants