getspacetime / spacetime Goto Github PK

Since we are able to explore/reflect a gRPC service with grpc-curl, this previous implementation of IGrpcExplorer needs to be cleaned up.

• Write scripts to publish a Mac executable / installer
• Add Mac build to Github Actions
• Automatically create release with Mac .app file

Once #31 is done, we should be able to add a "refresh" button near the "add service" button in the request pane. This should refresh all the services using the "simple" method in #31.

We added the ability to beautify responses in #10.

Implement the toggle setting using the "Paint" icon on the Response toolbar.

• Add toggle (either globally or per request)
• Save status of toggle
• Add unit tests for beautify + toggle
• This toggle should take effect during the request

Many code editors and applications allow for flexible panels. Support should be added to resize the request / response panes of the clients.

Currently, Spacetime supports adding new gRPC services using reflection. We now need support for updating these services.

Simple

• Right click on a service, the context menu should have an "update" menu item
• Clicking this menu item should refresh the service

Advanced

• Right click on a service, the context menu should have an "update" menu item with a submenu "update" and "update (advanced)" todo: choose better naming
• Clicking this menu item (advanced) should open a popup allowing a user to change the settings for the service. for now, just the host URL

Notes

• Simple method should not prompt the user again in most scenarios
• Should show a loading indicator for the service and a little checkmark when done
• Should show an error if something bad happened and let the user take an action

Describe the bug
When switching dark or light themes, the editor does not immediately switch themes

To Reproduce
Steps to reproduce the behavior:

1. Execute a request
2. Open the settings dialog
3. Switch the theme (dark to light or vice-versa)
4. Click OK
5. Themes for the app switch, editor does not
6. Click the header tab under the response or request
7. Click back to the editor, now the theme has switched.

Expected behavior
Theme for the editor should switch immediately after changing themes.
A clear and concise description of what you expected to happen.

Notes
This may be fixed by figuring out how to manually destroy and re-render the editor. Potentially with StateHasChanged?

I love Tailwind. That said, for consistency's sake, it's better for now to go all-in with using MudBlazor's components and styling system. MudBlazor is too hard to customize while using Tailwind and adds an additional piece of complexity, that quite simply I don't have the bandwidth to tackle.

• Replace containers with MudBlazor containers
• Replace utilities with MudBlazor utilities
  • Padding
  • Margin
  • Width
• Add CSS or reusable utilities where not found in MudBlazor
• Remove Webpack (we shouldn't need it after Tailwind is gone)
• TBD

Add support for secret headers, for example, if adding an Authorization header - you don't always need or want the value to be visible. These should be treated as secrets.

Pasting in to inputs on the REST client are causing the pasted contents to be duplicated.

1. Create a new request
2. Paste a URL in to the Request URL box
3. The pasted URL is duplicated
4. Add a header
5. Paste a value in to the value box
6. The pasted value is duplicated

OS: Mac
Windows appears to work fine. Could this be related to the performance issues seen on certain Macs?

MudBlazor supports nested lists and tree views. We should be able to utilize these components to be able to create folders for our requests.

This will require both UI changes and data structure changes.

UI

• Add new button/button group with the existing "add request" button for folder creation
• Add ability to move request into a folder or out of a folder
• Add ability to delete folder + contents
• Add warning for deleting folder with contents
• TBD

Data structure

• Add support for folder location on the SpacetimeRequest
• TBD

Currently, the dropdown only is closed when:

1. The user selects an option,
2. The user clicks the dropdown toggle again

Need to add some kind of clear overlay or wrapper that detects clicks anywhere outside of the element. Needs research in to the best/proper way to do this - hopefully without JS?

• Allow enable/disable of cert validation
• Enable ability to encrypt local database
• Move settings reset and db deletion to general tab

1. Run app for the first time / clean install
2. The app containers are "stacked" instead of side to side

When switching to MudBlazor and utilizing the List component, we lost the ability to sort requests.

• Add a drag handle element to the list
• Be able to reorder the items in the list
• Persist the order of the items

Note: I briefly tried the dropzone component in MudBlazor for this use case, but it crashed the app. Could use more investigation.

Integrate settings to allow configuration of logging & metrics

• Enable / disable logging
• Set logging level
• Enable / disable metrics (note: metrics is a future implementation)

Create an MSIX installer for Alpha builds - using a self signed certificate.

• MSIX Installer
• Certificate generated
• Documentation added

https://docs.microsoft.com/en-us/dotnet/maui/windows/deployment/overview

The Monaco editor tends to switch from the right pane to the left pane.

Further investigation needed. It seems to occur when the pane disappears, e.g. when switching to the headers tab and back or vice-versa.

• Windows
• Mac

Add support for toggling headers on and off for a request. Currently, only deletion is allowed.

• Add a checkbox to enable / disable
• Modify UX to indicate header is disabled

In an effort to migrate custom components to MudBlazor, support for editing request names was intentionally removed.

• Allow the user to click in the MudListItem to edit the text. Currently, this component may only support text fields.

Should also support Put, Patch, Delete, Head, Options

Unsure if anything needs to be done here, besides wait for support in the virtual machine for the latest SDK version.

In the current flow, we add all services found in the reflection service of a gRPC server to the collection.

• Detect matching services and default to update them
• Allow user to select which services / methods to add

Current flow