PricingBlog

Show/hide via context or attributes not working atm

  • klevelandbishop-1445102321422827650

    Kleveland Bishop

    10 months ago

    https://supercut.ai/share/boomin/9IUTZRY8rJG8sWZYbRarzv

    I'm using Show/Hide throughout my single-page application to allow my users to navigate through the app. I notice when I'm trying to show/hide components that are on the 2nd or 3rd path, show-hide stops working, ie those components still render on the UI. Is there a way to bulletproof show-hide even with deeply nested components?
    My entire route nav system is currently built off attributes, this was after I was experiencing the same issue using context to give the app intel on what the current path is
  • lucasg-1445105834106556638

    Lucas G

    10 months ago

    Are you able to invite to project
  • klevelandbishop-1445105905170387004

    Kleveland Bishop

    10 months ago

    The current route is being set via a workflow that takes in params
    1445105904511877221-image.png
    1445105904906403881-image.png
  • yea !
  • lucasg-1445105985260748942

    Lucas G

    10 months ago

    I'd prefer to do this over Contexts since attribute drilling is annoying in comparison
  • Strange that you had issues with it
  • klevelandbishop-1445106058061152377

    Kleveland Bishop

    10 months ago

    whats your email, same man. would be a dream in context could work
  • lucasg-1445106083495411743

    Lucas G

    10 months ago

    lucas
  • is username
  • klevelandbishop-1445106318200275094

    Kleveland Bishop

    10 months ago

    k
  • klevelandbishop-1445106705955295326

    Kleveland Bishop

    10 months ago

    invite sent
  • lucasg-1445106919281918043

    Lucas G

    10 months ago

    I'll take a look in about an hour when I get on comp 👍
    🙌1
  • klevelandbishop-1445108161626378415

    Kleveland Bishop

    10 months ago

    thanks man, take your time!
  • lucasg-1445141124883681280

    Lucas G

    10 months ago

    Took a look and there's something weird going on
    1445141124472766606-image.png
  • Not sure what these errors belong to
  • But the showWorkspace log shows that the component's condition is false
  • lucasg-1445142278157897840

    Lucas G

    10 months ago

    Recreated the formula exposed in the context and it works
  • So something might be wrong with the original formula under the hood
  • Team toddle might want to investigate
  • lucasg-1445143229782823004

    Lucas G

    10 months ago

    @Kleveland Bishop can you test the show/hide conditions with the newRoute formula exposed via context on the places you were seeing the issue to see if it's the original formula
  • klevelandbishop-1445143445466513439

    Kleveland Bishop

    10 months ago

    ok checking now
  • lucasg-1445143465838117008

    Lucas G

    10 months ago

    For example
    1445143465582137364-image.png
    🔥1
  • That seems to be fine for your workspace condition now
  • klevelandbishop-1445144321689911471

    Kleveland Bishop

    10 months ago

    That seems to have solved it, only thing that has popped up is the table( and any path after the uuid path) only renders on refresh, notice that?
  • klevelandbishop-1445144657909518357

    Kleveland Bishop

    10 months ago

    could just be a data fetching issue with the new structure, i think im calling the api off the old route system
  • klevelandbishop-1445148052863189105

    Kleveland Bishop

    10 months ago

    ill do a quick refactor off newRoute and keep you updated
  • klevelandbishop-1445153347475607552

    Kleveland Bishop

    10 months ago

    working like a charm off context with newRoute! thanks man, no more hanging components
    👍1
  • lucasg-1445154972898431006

    Lucas G

    10 months ago

    Don't delete current_route
  • There seems to be something wrong with it or its context that the team might want to look at
  • Not sure why it wouldn't work otherwise as the new formula is the same thing
  • klevelandbishop-1445155463808290898

    Kleveland Bishop

    10 months ago

    right, ok i wont delete it
  • interesting, ok
  • lucasg-1445155749406965760

    Lucas G

    10 months ago

    Should be fine to delete all those other test ones you had though, even the attributes (if you prefer to use context instead of drill attributes down)
  • klevelandbishop-1445156073869934634

    Kleveland Bishop

    10 months ago

    i absolutely would like to use context, drilling wasn't terrible but much happier not to drill on every single component