Skip to content

No error warning when API Call is missing a parameter #7453

Description

@JeanLouisPiquet78125

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Following the change initiated by Flutterflow for securing API Calls token (Supabase token key), after making all the changes in API Call dashboard, there is no warning indicating with API Call is missing a prameter which is obliging users to go in painfull process of checking page by page, action by action what needs to be updated/

While I believe that changes in API Call was needed security wise, absence of warning on API Call paramter is a critical flaw...

Expected Behavior

At least, once the changes are made atteh API Call level ther must be a red or orange warning informing the user where to update parameters.

Steps to Reproduce

  1. You removed the anon key and replacd it by [token]
  2. Do it for let's 40+ API Calls;
  3. Enjoy the results.

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT40i+fl6ot2mNtF7c7qacEw+So5KWI/a+c3jMJ7aCsofePrOpkAf8/7UFtUcO2+dHxLfGGZ+DkX/MrGjeD2Gvk6C0iAfJxk+pNcdzyUQly5Spi2DpS3b3wlGeNRfkyO352JmxRDNsRfWnwS71OXe++9bAXdQbL6IkVEMua4XdeK2SrDX1iXc2URm05KZDPz

Visual documentation

No visual documentation otherwise this bug won't be raised...

Environment

- Bug is environment agnostic as it pertains to FF behavior not link with any system

Additional Information

Instead of debveloping nerw fancy useless functions... Please try at least to solve painful processes and flaws.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: needs triageA potential issue that has not been confirmed as a bug.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions