fix(platform): Fields with default value are not set to advanced by default

[majdyz]

#8739 causes input fields that are supposed to be an advanced field end up being a mandatory field:

*See the retry count field here.

Changes 🏗️

Set the advanced field on each input field, and set the default value using this logic:

• If it has a default value, set it to True.
• otherwise, False.

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • ...

Example test plan

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

For configuration changes:

• .env.example is updated or already compatible with my changes
• docker-compose.yml is updated or already compatible with my changes
• I have included a list of my configuration changes in the PR description (under Changes)

Examples of configuration changes

• Changing ports
• Adding new services that need to communicate with each other
• Secrets or environment variable changes
• New or infrastructure changes such as databases

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 8739 - Partially compliant Compliant requirements: Fix issue where input fields that should be advanced are showing as mandatory Non-compliant requirements: Hide "advanced" toggle on blocks if there are no advanced inputs Requires further human verification: Verify in UI that advanced toggle is properly hidden when no advanced inputs exist Verify that fields with default values are correctly marked as advanced in the UI

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Logic Validation Verify that the new advanced field logic correctly handles all edge cases, especially when both default and default_factory are provided if default is PydanticUndefined and default_factory is None: if advanced: raise ValueError("Advanced fields must have a default value.") advanced = False elif advanced is None: advanced = True

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	e497915
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/67740b5410a8ea0008cc4109

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	e497915
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/67740b543fd33e0009636393

[Swiftyos]

We made a conscious choice to allow fields with default values that aren’t marked as advanced. There are times when we don’t want to automatically mark a field as advanced while still providing a default value.

Does this updated version still allow inputs with default values that aren’t advanced?

[majdyz]

We made a conscious choice to allow fields with default values that aren’t marked as advanced. There are times when we don’t want to automatically mark a field as advanced while still providing a default value.
Does this updated version still allow inputs with default values that aren’t advanced?

Yes, This is the only reason I added this advanced field feature.

But #8739 makes all the values with default non-advanced unless it's explicitly defined to do so, which is not the expectation.