Adding server url page #23

tepichord · 2026-02-12T13:23:45-08:00

tepichord commented

2026-02-12 13:23:45 -08:00

Closes #10

Adds shadcn components needed for basic server connection card
Sets up Tauri store on the rust end (copying petite but making it lazier)
Adds some commands to get and set the server url
Adding SWR and using it to fetch the url on load
Upon loading will redirect to home, but there's no way to clear the url value except editing the file manually in AppData/Roaming/systems.graham.microclimate/config.json will need to add a button in settings or maybe just in layout temporarily to change server url

Closes #10 - Adds shadcn components needed for basic server connection card - Sets up Tauri store on the rust end (copying petite but making it lazier) - Adds some commands to get and set the server url - Adding SWR and using it to fetch the url on load - Upon loading will redirect to home, but there's no way to clear the url value except editing the file manually in `AppData/Roaming/systems.graham.microclimate/config.json` will need to add a button in settings or maybe just in layout temporarily to change server url

tepichord added 4 commits

2026-02-12 13:23:45 -08:00

Importing shadcn components 0970bf0f7b

Building out server connection form a4826450e1

Working Set 1

Setting up Tauri store b565c60c42

Calling gRPC procedures to connect 18117f25d1

tepichord force-pushed issues/10-server-url from 18117f25d1 to 570c3d24a0

2026-02-12 13:24:19 -08:00

Compare

tepichord commented

2026-02-12 13:25:50 -08:00

"Calling gRPC procedures to connect commit" isn't real, look at the Commits tab for the actual up-to-date commit list

tepichord added 2 commits

2026-02-13 15:59:31 -08:00

Change SWR to react-router data-loader 0f067fa6e9

Adding button to change server url 0d8400821f

tepichord commented

2026-02-13 16:05:20 -08:00

Swapped SWR out for a react-router data loader as I couldn't find a nice way to use SWR without caching the value.

- Swapped SWR out for a react-router data loader as I couldn't find a _nice_ way to use SWR without caching the value.

tepichord reviewed

2026-02-13 16:05:27 -08:00

app/routes/set-server-url.tsx Outdated

					
				@ -2,0 +23,4 @@

				  const navigate = useNavigate();

				  const [url, setUrl] = useState("");

				  const { data, error, isLoading } = useSWR("get_server_url", fetcher);

Don't pass a cache key, use null as we don't want caching
inline the fetcher
add return type specifier to fetcher

- Don't pass a cache key, use null as we don't want caching - inline the fetcher - add return type specifier to fetcher

tepichord marked this conversation as resolved

app/routes/set-server-url.tsx Outdated

					
				@ -2,0 +25,4 @@

				  const { data, error, isLoading } = useSWR("get_server_url", fetcher);

				  // console.log(`"${data}"`, error, isLoading);

Delete

tepichord marked this conversation as resolved

tepichord force-pushed issues/10-server-url from 0d8400821f to edbf32f37f

2026-02-13 16:08:56 -08:00

Compare

puregarlic requested changes

2026-02-13 20:05:46 -08:00

Dismissed

puregarlic left a comment

Just a few things to cleanup, in addition to the anyhow comments. I've already discussed ts-rs with @seb, so at the very least we'll want to get that in for complicated commands--though it's not necessarily required for your simple commands at this time though. I'm open to discussion as to how to proceed, but again, my perspective is that there's no time like the present to be thorough about errors.

Just a few things to cleanup, in addition to the `anyhow` comments. I've already discussed `ts-rs` with @seb, so at the very least we'll want to get that in for complicated commands--though it's not necessarily required for your simple commands at this time though. I'm open to discussion as to how to proceed, but again, my perspective is that there's no time like the present to be thorough about errors.

app/routes/layout.tsx Outdated

					
				@ -1,1 +6,4 @@

				export default function Layout() {

				  const navigate = useNavigate();

				  const handleOnClick = async (e: React.SyntheticEvent) => {

This is a good candidate for a clientAction.

This is a good candidate for a `clientAction`.

app/routes/set-server-url.tsx Outdated

					
				@ -2,0 +32,4 @@

				  const navigate = useNavigate();

				  const [url, setUrl] = useState("");

				  const handleSubmit = async (e: React.SyntheticEvent) => {

This should be a clientAction as well

This should be a `clientAction` as well

src-tauri/Cargo.toml Outdated

					
				@ -28,2 +28,4 @@

				tonic-prost = "*"

				tokio = { version = "1.0", features = ["macros", "rt-multi-thread"] }

				tauri-plugin-store = "2"

				anyhow = "1.0.101"

Not gonna lie... Not a huge fan of anyhow. I know it's convenient, but we should start on the right foot of handling our errors correctly.

I know with Tauri commands especially, this is annoying, because the error result needs to derive serde's Serialize. This means:

You often can't return the error directly,
You have to define an extensive Error enum that encompasses all of the possible failures, and then
You don't get decent types in JS land, so you don't even know what the errors are when you need to present them.

I used ts-rs in petite to make this easier. At the module level, you can define a custom error enum that will handle any un-derived errors into strings, with added metadata to describe the practical effect of the error. Then, because that enum is Serialize-able, ts-rs can generate a type you can use in JS land to check for different error conditions. And also--you can now get strongly-typed objects from structs for command payloads.

I know it feels a bit excessive, but I would really us rather get in the habit of handling these errors the right way sooner rather than later.

Not gonna lie... Not a huge fan of `anyhow`. I know it's convenient, but we should start on the right foot of handling our errors correctly. I know with Tauri commands especially, this is annoying, because the error result needs to derive serde's `Serialize`. This means: 1. You often can't return the error directly, 2. You have to define an extensive `Error` enum that encompasses all of the possible failures, and then 3. You don't get decent types in JS land, so you don't even know what the errors are when you need to present them. I used [ts-rs](https://github.com/Aleph-Alpha/ts-rs) in `petite` to make this easier. At the module level, you can define a custom error enum that will handle any un-derived errors into strings, with added metadata to describe the practical effect of the error. Then, because that enum is `Serialize`-able, ts-rs can generate a type you can use in JS land to check for different error conditions. And also--you can now get strongly-typed objects from structs for command payloads. I know it feels a bit excessive, but I would really us rather get in the habit of handling these errors the right way sooner rather than later.

Yeah makes sense, I'll remove anyhow, but custom errors always seem like such a huge waste of time. In the end I've never seen use of custom error types. I always just need the message, and the stack trace. And I hate the effort of elaborating all these different categories of errors and then their use cases just seem unusable because on the receiving end you want to split out error handling based on the category of error but end up doing basically the same thing. After all, what can you really do when there's an error? it's not like the client is gonna fix that.

Griping aside, since tauri::command doesn't even allow anyhow errors it's definitely a non-starter.

Yeah makes sense, I'll remove anyhow, but custom errors always seem like such a huge waste of time. In the end I've never seen use of custom error types. I always just need the message, and the stack trace. And I hate the effort of elaborating all these different categories of errors and then their use cases just seem unusable because on the receiving end you want to split out error handling based on the category of error but end up doing basically the same thing. After all, what can you really do when there's an error? it's not like the client is gonna fix that. Griping aside, since tauri::command doesn't even allow anyhow errors it's definitely a non-starter.

src-tauri/src/lib.rs Outdated

					
				@ -12,0 +24,4 @@

				            Ok(())

				        })

				        .invoke_handler(tauri::generate_handler![

				            greet,

We can probably yoink this guy now

tepichord marked this conversation as resolved

seb referenced this pull request

2026-02-13 23:26:09 -08:00

26-channel-display-tauri #24

seb commented

2026-02-14 19:13:33 -08:00

Can we merge #24 in here prior to merging to main?

puregarlic commented

2026-02-15 14:21:15 -08:00

@seb wrote in #23 (comment):

Can we merge #24 in here prior to merging to main?

I'm for this. You'll need to coordinate with @tepichord.

@seb wrote in https://git.gloom.garden/puregarlic/microclimate/pulls/23#issuecomment-368: > Can we merge #24 in here prior to merging to main? I'm for this. You'll need to coordinate with @tepichord.

seb added 1 commit

2026-02-17 15:33:52 -08:00

26-channel-display-tauri (#24 ) 5e662a432e

Closes #26.

This PR implements a client for connecting to the channel server, registers it with the AppState, and exposes the behavior through Tauri commands.

Reviewed-on: #24
Reviewed-by: Graham <red.iron2345@fastmail.com>
Co-authored-by: Sebastian Benjamin <sebastiancbenjamin@gmail.com>
Co-committed-by: Sebastian Benjamin <sebastiancbenjamin@gmail.com>

puregarlic added a new dependency

2026-02-18 10:25:47 -08:00

#30 Integrate Storybook and ts-rs

puregarlic referenced this pull request

2026-02-18 10:26:42 -08:00

Integrate Storybook and ts-rs #30

puregarlic added the

labels

2026-02-18 10:27:13 -08:00

puregarlic added this to the Gehrman (Feasibility Test) milestone

2026-02-18 10:40:06 -08:00

tepichord added this to the Feature Development project

2026-02-18 16:15:23 -08:00

tepichord self-assigned this

2026-02-18 16:15:26 -08:00

tepichord added 2 commits

2026-02-18 16:39:36 -08:00

Adding error types 5023835f1f

Creating clientActions for navigation 4ddf795f59

tepichord force-pushed issues/10-server-url from 4ddf795f59 to 79a1ca3d88

2026-02-18 16:51:55 -08:00

Compare

puregarlic approved these changes

2026-02-18 16:52:39 -08:00

puregarlic left a comment

LGTM

puregarlic added 1 commit

2026-02-18 16:56:11 -08:00

Channel UI (#33 ) 54a371846d

Closes #7.

Reviewed-on: #33
Reviewed-by: Graham <red.iron2345@fastmail.com>
Co-authored-by: Sebastian Benjamin <sebastiancbenjamin@gmail.com>
Co-committed-by: Sebastian Benjamin <sebastiancbenjamin@gmail.com>