PricingBlog

Publishing a branch to main corrupted my project and I can't recover.

  • marta_filipe-1486504545940148275

    Marta_Filipe

    18 days ago

    After publishing branch mecanismo-filtro-dinamico, one formula (allDropdownsSelected) was renamed to an internal ID (Bnlbi3) and a ghost "Untitled" formula appeared. Browser throws TypeError: null is not an object (e.arguments.map) in formula.ts:407 on every page load. My entire configurator component is broken.

    The original branch was auto-deleted on publish — I have no way to go back to the working version. Weeks of work on this component.


    Is there any way to restore a deleted branch? Or fix main without rolling back weeks of work?

    need help — this is blocking our entire project.
  • mikkeltoddle-1486594189960548503

    Mikkel

    18 days ago

    Hey Marta! I am sorry to hear about that. Can I see your project? Then I will try and figure out what has happened. You might need to invite me - "mikkel"
  • mikkeltoddle-1486594704807170079

    Mikkel

    18 days ago

    Also, can you describe the steps up to publishing the branch? Did you have to sync with main before publishing? Did you have any conflicts that you resolved as part of syncing? Did you "reset" any files right before publishing? That might make it easier for me to know what to look for.
  • marta_filipe-1486628558985232394

    Marta_Filipe

    18 days ago

    hey Mikkel , thank you for rapid respond. I just send you the invite. What I did was in the version control , add a comment "drop eatable a familia de difusão funciona" and publish branch and after create a new one scalling-todas-familias.
  • mikkeltoddle-1486628697736745102

    Mikkel

    18 days ago

    Alright. I will have a look.
  • marta_filipe-1486629002046083112

    Marta_Filipe

    18 days ago

    Thanks. the probem is in tarifas page, the drop.
  • mikkeltoddle-1486630156029136977

    Mikkel

    18 days ago

    allDropdownsSelected seems to be correctly named. Where can I find the internal ID formula?
  • marta_filipe-1486631656780599328

    Marta_Filipe

    18 days ago

    What do you mean by internal ID formula?
  • Tod-1486631659884249099

    Tod

    18 days ago

    Great job @Marta_Filipe! Your contribution to the Nordcraft Community just made you advance to Community Level 1! 🌲
  • mikkeltoddle-1486631818932523058

    Mikkel

    18 days ago

    The formula that was renamed to an internal ID.
  • mikkeltoddle-1486632862105997354

    Mikkel

    18 days ago

    Do you have time for a quick call? I think I need to understand your issue better.
  • marta_filipe-1486633407856377906

    Marta_Filipe

    18 days ago

    The AI assistant analysis found that the formula allDropdownsSelected does not exist by that name in the component. Instead it found an unnamed formula with internal ID Bnlbi3 that appears to have similar logic. It's in components/tarifas on the scaling-todas-familias branch (and also on main since the branch was created from main after the publish).

    Also to answer your earlier questions about the publishing steps:
    - I did NOT have to sync with main before publishing. There were no conflicts shown.
    - I did NOT reset any files.
    - I simply went to version control, added the comment "drop eatable a familia de difusão funciona" and clicked publish.
    - The branch mecanismo-filtro-dinamico was auto-deleted after publish.
    - I then created a new branch scaling-todas-familias from main.
    - When I tested the new branch in the browser, the dropdowns were gone and the console showed TypeError: null is not an object (evaluating 'e.arguments.map') in formula.ts:407.

    The formula allDropdownsSelected was created manually in the visual editor during an earlier session. It uses Every over activeFilterConfig to check if all visible filters have a selection.
  • marta_filipe-1486634690063634543

    Marta_Filipe

    18 days ago

    I can't do a call right now. Would 10:30 AM Portuguese time (GMT+0) work for you?
  • mikkeltoddle-1486635575682404402

    Mikkel

    18 days ago

    Yep!
  • marta_filipe-1486635897079464037

    Marta_Filipe

    18 days ago

    Some extra context to help you while I'm away:

    The component is a product configurator with cascading dropdown filters. The page /tarifas/:slug loads a product by slug, queries Supabase via GraphQL, and renders dynamic dropdowns based on the product's available variations. You can test with /tarifas/dtr.

    Before publish, everything worked — dropdowns rendered, cascade logic worked, results showed correctly. After publish, all dropdowns disappeared.

    The component has 6 formulas, 1 workflow (handleFilterChange), 2 variables (selections, openDropdownId), and 1 API (query_dropdowns). The AI analysis confirmed 5 of 6 formulas are intact — only allDropdownsSelected appears corrupted.

    I have to step out now but I'll be available for the call at 10:30 AM Portuguese time. Thank you!
  • mikkeltoddle-1486639217848094780

    Mikkel

    18 days ago

    I believe I have found out what the problem is.
  • marta_filipe-1486674842605457579

    Marta_Filipe

    18 days ago

    Thanks you 😄 ! It works 😄
  • mikkeltoddle-1486679172159115334

    Mikkel

    18 days ago

    🎉