Skip to content

Conversation

geodem127
Copy link
Contributor

@geodem127 geodem127 commented Jul 5, 2025

  • Schema: Create Block Type Card - Field list item
  • Schema: Create Option Cards
  • Schema: Add "Integration Field" to the field type selection options, tooltip and form
  • Schema: Create Display Type Options Selection Modal
  • Schema: Form Dialog (Connect to API)
  • Schema: Form Dialog (Display Type Selection)
  • Schema: Form Dialog (Configure Display Options)
  • Schema: JSON view - Edit Dialog

  • Content:Item Selection Dialog
  • Content: Field View Components
  • Content: JSON view - Edit Dialog

Technical Specs: https://docs.google.com/document/d/1xynOhoDtj6TJB_tUrvx_rPncL4sIT156TdPd3qlDaek/edit?usp=sharing

ADD FIELD:


Integration-Field-Add-Field.mp4

SELECT ITEMS:


Integration-Field-Select-Items.mp4

agalin920 and others added 30 commits April 14, 2025 22:04
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
}, obj);
}

export const fetchApi = async <T = unknown>({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I question the value of this abstraction, it’s mildly useful at best, but it introduces some questionable design choices that might hurt more than help.

Its a redundant abstraction and you lose flexibility without gaining much.


const { endpoint, headers, type, keyPaths } = config;

const generateItemId = useCallback(
Copy link
Contributor

@agalin920 agalin920 Aug 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is really needed you could just use uuid library that we have instead of this complex logic.

Although I would ask you to question this further and see if this is really needed or if it can all be index based

error,
children,
}: {
name?: string;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use your standard prop typing pattern. FieldWrapperProps

setType,
closeForm,
}: {
activeStep: number;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here regarding prop typing

@geodem127 geodem127 requested a review from agalin920 August 22, 2025 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Improvement to an existing feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Schema: Integration Field

3 participants