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

Publish JSON schema to support IDE integration. #860

Open
1 of 5 tasks
Uh-little-less-dum opened this issue Dec 15, 2024 · 3 comments
Open
1 of 5 tasks

Publish JSON schema to support IDE integration. #860

Uh-little-less-dum opened this issue Dec 15, 2024 · 3 comments
Labels
approved feature Feature request approved for development

Comments

@Uh-little-less-dum
Copy link

Description

This isn't a bug, but rather a feature request. Would it be reasonable to publish a json schema for the configuration to support IDE integration? If one exists, maybe document that better, because for the life of me I couldn't find it. This is still an awesome project regardless.

Mockery Version

2.50.0

Go Version

1.23.2

Installation Method

  • Binary Distribution
  • Docker
  • brew
  • go install
  • Other: [specify]
@LandonTClipp
Copy link
Collaborator

I haven't published a schema but I have thought about it and I think it would be a great idea! I won't have time to look into it for a while but I'd appreciate if anyone wanted to tackle that.

@LandonTClipp LandonTClipp added the approved feature Feature request approved for development label Dec 16, 2024
@Uh-little-less-dum
Copy link
Author

I haven't published a schema but I have thought about it and I think it would be a great idea! I won't have time to look into it for a while but I'd appreciate if anyone wanted to tackle that.

Usually I'd be all in, but I've worked with Go for a few weeks at this point, and I'm not sure the schema I'd create would be accurate. Json tags make perfect sense to me, but for the life of me I'm not quite sure what exactly that mapstructure package is actually doing.

@LandonTClipp
Copy link
Collaborator

Unfortunately mapstructure was needed after I made a poor decision of using viper for configuration parsing. As you'll see, the config parsing is a complete mess and I hope to make it more sane in v3, which is under active development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved feature Feature request approved for development
Projects
None yet
Development

No branches or pull requests

2 participants