seed icon indicating copy to clipboard operation
seed copied to clipboard

A Rust framework for creating web apps

Results 75 seed issues
Sort by recently updated
recently updated
newest added

**Motivation** - [x] Reduce boilerplate. - [x] [Slice patterns](https://thomashartmann.dev/blog/feature(slice_patterns)/) will be stabilized in the next Rust version (`1.42.0`). - [x] Seed should take into account base path (https://github.com/seed-rs/seed/issues/369). - [...

API design

I did a review of the url-api. My motivation is that I did not understand how this module is intended to be used and saw an opportunity to improving discoverability...

enhancement
API design

I have a case where I need to check that the content-type of a response is `application/json` in order to ensure validity. My current method of doing this is to...

help wanted
missing functionality
API design

### Wouldn't you just prefer to simply set styles... ```rust let style = S .background_color("red") .margin("2px") .padding("8px"); button![style, "Hello!"] ``` ### ...pretty clean! This issue details a proposed styling system...

Seed chat channel `#app-atchitecture`: > I'm facing this big rabbit hole called "Forms" and I want to make something reasonably simple that gets the job done without a lot of...

help wanted
API design

@MartinKavik Off-topic, I am wondering if seed will ever look into not using virtual DOM? _Originally posted by @pickfire in https://github.com/connorskees/grass/issues/4#issuecomment-653845842_ --- I/we understand VDOM as a big implementation detail....

question

Resources: - https://www.smashingmagazine.com/2018/02/sse-websockets-data-flow-http2/ - https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events - https://www.ably.io/concepts/server-sent-events - https://kaazing.com/kaazing.io/doc/understanding-server-sent-events/

help wanted
missing functionality

#513 [Relevant discussion](https://github.com/seed-rs/seed/pull/513#discussion_r467563396) The referred to PR was created in response to `fetch::Response` breaking my workflow when a `Message` had it in an assosciated type. For example: ```rust #[derive(Debug)] enum...

enhancement

See #506 Currently, the output of `log!` is not Just Right™ due to manner in which Rust and JS interact (to my understanding). Though things are in a good place...

In the `fetch()` example in documentation: ```rust async fn send_message(new_message: String) -> fetch::Result { Request::new(get_request_url()) .method(Method::Post) .json(&shared::SendMessageRequestBody { text: new_message })? .fetch() .await? .check_status()? .json() .await } ``` Similarly, you...

enhancement
docs