Will Guardrails pro have a way of reporting via a LSP server for in editor feedback?
GRP will have more than one way of reporting. LSP (or a purpose-build plugin) is on the primary list. We’re interested in it supporting in-editor reporting for as many editors as possible. Definitely Cursive, Emacs, Vim, and VSCode. It will also probably have a web-based interface for control/reporting that will make is usable with any editor period. Choice of implementation for integration is not certain yet. Still working on the primary features of checking.
@tylernisonoff STD component should not care, so I'm not sure what the specific problem is. You are implying that something isn't working, or that the API isn't ideal?
hmm its not working...
if I go to <http://localhost:3000/project/ffffffff-ffff-ffff-ffff-000000000300>
It'll get redirected to
<http://localhost:3000/project/:id?_rp_=WyJeICJd&>
and in the dev console i see
Insufficient route parameters passed. Resulting route is probably invalid. com.example.ui.project-forms/Project
But if if i go to the full url i got when I use the link from rroute/route-to!
, <http://localhost:3000/project/ffffffff-ffff-ffff-ffff-000000000300?_rp_=WyJeICIsIn46aWQiLCJ%2BdWZmZmZmZmZmLWZmZmYtZmZmZi1mZmZmLTAwMDAwMDAwMDMwMCJd&>
it works
ok, yeah, that’s a but in rroute then. I didn’t remember it trying to mess with non-RAD components in any way
but I must have set up some plumbing I don’t remember
heh its funny, if i then hit the back button, it goes back to the URL without params (makes sense), but then works! 😛 so restoring the route works, its just something weird on pageload
seems like the codepath is:
html5_history.restore-route!
converts url to
{:route ["projects" "uuid-str"] :params {}}
which calls
(defn apply-route!
"Apply the given route and params to the URL and routing system. `saved-route` is in the format of
the return value of `url->route`. Returns true if it is able to route there."
[app {:keys [route params] :as saved-route}]
(if-let [target (dr/resolve-target app route)]
(do
(routing/route-to! app target params)
we resolve the right target (my Project component)
But params is still {}
Is apply_route!
where we should be somehow translating the raw route into the appropriate params map for the given target?
it seems like maybe we want something like:
let [target (dr/resolve-target app route)]
but a function that returns not just the target, but also the params for that target given the raw route?Hey folks, anyone knows how to express CSS pseudo-element properties in a fulcro component’s :css
?
e.g.: .icon::before {...}
(defsc Icon [this {:keys ...}]
...
{:css [[:.icon {:color "red"}
[:&::before {:content "hello"
:color "white"}]]})
I tried this and a few other ways (importing garden.selector/before
).
I think what’s not clear to me is the forms that fulcro (or garden?) expect to be given, to then allow the rest of the normal mungling flow in the rendered css.