This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-26
Channels
- # asami (3)
- # babashka (3)
- # beginners (45)
- # boot (3)
- # calva (6)
- # clojure (26)
- # clojure-dev (16)
- # clojure-europe (15)
- # clojure-norway (6)
- # clojure-uk (6)
- # clojurescript (34)
- # community-development (4)
- # conjure (3)
- # datascript (4)
- # datomic (4)
- # emacs (21)
- # events (1)
- # fulcro (16)
- # graalvm (5)
- # jackdaw (1)
- # kaocha (5)
- # lsp (74)
- # malli (8)
- # nbb (37)
- # off-topic (50)
- # pathom (5)
- # reagent (19)
- # ring (1)
- # shadow-cljs (60)
- # sql (3)
I don’t know how recursive calls to parse work. you might ask on the #pathom channel.
I asked already and it didn’t seem to be surprising to people.
@U0CKQ19AQ it’s working as expected if I do this:
(parser
{:fulcro-parser parser}
[{[:account/id "EJ2NCAPPk6WSpuv7bwvHAK8sVGV4htZFir242pVCzUEb"]
[:account/stakes]}])fulcro-parser in the :account/stakes resolver. Would you accept a PR to always have this?nvm, it couldn’t work like this. I’m kind of lost here. We rely heavily on this feature. I’ll see what I can do.
They said it’s supposed to work.
I am deploying my apps to be relative to context-root. Not my choice, I just have to do it that way.
So I start immutant.web {:port 3000, :host "0.0.0.0", :path "/apps/monitor"}
I need that url is /report/ is set as /apps/monitor/report/
So how can I solve the history context-root handling;
in index.html I will write <script>const csroot='/apps/monitor' </script>
Now I have to modify history rewriting. Is html5-history/apply-route! right candidate?
The adapting between URL and your internal routing can be a generalized function in plain Fulcro, but if you’re using RAD, then yes you’ll have to copy some of the code there and augment it. I don’t have a hook for prefixing built in. Happy to take a PR to add that option to the system. It already has an option to make the routes hash-based, so you could add one for base-url-prefix
might want to start carrying those things around as options 😛 But as you can see it is protocol-based and very simply, so implementing your own version isn’t more than 30 lines of code…but in this case augmented option is fine.
@U0CKQ19AQ please take a look at https://github.com/fulcrologic/fulcro-rad/compare/develop...janezj:fulcro-rad:prefix-route I have tested with prefix and without.
Great. So, I would probably do a few things at this point, since the arglist is getting a little long here. I don’t make breaking changes to existing API, so here’s what I’d do:
• Instead of adding a parameter to html5-history (which is a non-breaking change, but is starting to get messy) I’d make a new function named new-html5-history that takes a single arg, a map, and put all three options in there. If you want prefix, you use the new constructor function.
• I’d refactor the old function html5-history to call the new one, and put a comment in the docstring that you should prefer using the new one, since it supports more options
• Make sure the docstrings include details on what the option does.
But I have a huge problem with reports, I would like to have a hidden column, or [{:station/status (comp/get-query Status)}] to be inserted into into generated load! is it possible?
See ro/row-query-inclusion and ro/query-inclusions. You can add queries for whatever you want, and if you don't list the RAD attributes under ro/columns, they are "hidden columns".