Martin Kavík

> if you guys have any suggestion Try to make it as simple as possible.. I didn't think about it so much to write some reasonable advice and we'll see...

4th solution (as designed - https://github.com/seed-rs/seed/issues/312#issuecomment-565832751): ```rust input![ A.dir().rtl(), A.type_().number(), A.type_().content_type().text_css(), A.required(true), A.step(0.2), ] ``` - Doesn't pollute `use` and local scope. - Autocomplete friendly. - Respects conventions for keywords...

> ```rust > input![ > // what's the result ? what's the attribute value we get here ? > A.dir(), > // what about this attribute > A.type_(), > ]...

Yeah, just small docs/comments changes. However they on relatively many places. I would be glad if you do it and it would be also better because I haven't encountered those...

I would just open VS Code, press `Ctrl+Shift+F` and write `Msg, Option`.. it should be enough I hope.

I think `data-target` is a specific Bootstrap attribute that leverages [data-*](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/data-*) attributes (please correct me if I'm wrong). Perhaps we can add a helper like `At::data("xx", "yy")` that generates `data-xx="yy"`...

hi @tommket! There is a bit older, but still very relevant issue about the new API design. See this comment in the issue to have an idea: https://github.com/seed-rs/seed/issues/525#issuecomment-684040068. Notice especially...

I can't reproduce it. Make sure the file `my-project/pkg/package.js` exists. `package,js` is generated only on successful build. When it's missing, dev server returns HTML hence the error. And I would...

> "3. Prepare your project for work" doesn't have the step of building the /pkg stuffs. Build step should be a part of `3. Open a second terminal tab and...

> So it might be nitpicky though, swapping the step 2. and 3. could be more helpful. But then the 4. step wouldn't make sense because you see errors only...