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

GUI #102

Open
2 tasks done
atyminski opened this issue Jun 24, 2022 · 3 comments
Open
2 tasks done

GUI #102

atyminski opened this issue Jun 24, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@atyminski
Copy link
Contributor

Prerequisites

  • I have written a descriptive issue title
  • I have searched existing issues to ensure a similar issue has not already been created

Description

Mockaco allows to edit mocks by editing files which requires using locally installed editor. Maintaining higher number of mocks becoming slightly complicated.

Proposed solution

A web based GUI/editor that helps to setup mocks, hosted by the Mockaco instance: _mockaco/gui

Monaco Editor could be used as response body editor that can help introduce syntax highlighting.

Alternatives

  • Visual Studio Code extension

Additional context

I've prepared initial version just with hosted blazor app without any new functionality, you can find it here .
This feature requires API implementation #66 .

@atyminski atyminski added the enhancement New feature or request label Jun 24, 2022
@atyminski
Copy link
Contributor Author

@natenho if you like the idea, I'm happy to continue the implementation.

@natenho
Copy link
Owner

natenho commented Jun 26, 2022

@atyminski Awesome, go ahead! The syntax highlighting might be challenging, but it would be a great feature.

Besides, do you have any idea on how could we deploy the GUI? Should it be an option to the main binary (e.g. Mockaco --gui)? Or should it be a completely different tool?

@atyminski
Copy link
Contributor Author

I added GUI as a build-in feature and it is hosted by Mockaco on `_mockaco/gui' endpoint when you start main binary, without any additional options - it seems to be the most convenient way to use it. We can decide later as it is another csproj 🙂 If it makes Mockaco "too heavy", we will move it to a separate binary.

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

No branches or pull requests

2 participants