-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Content types should have default values for Literal type fields #1731
Copy link
Copy link
Closed
Labels
P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featureenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedv2Ideas, requests and plans for v2 of the SDK which will incorporate major changes and fixesIdeas, requests and plans for v2 of the SDK which will incorporate major changes and fixes
Metadata
Metadata
Assignees
Labels
P1Significant bug affecting many users, highly requested featureSignificant bug affecting many users, highly requested featureenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedv2Ideas, requests and plans for v2 of the SDK which will incorporate major changes and fixesIdeas, requests and plans for v2 of the SDK which will incorporate major changes and fixes
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
Content types like
TextContentandImageContentrequire passingtype="text"ortype="image"explicitly, even though these are single-valueLiteraltypes.Current definitions:
Current usage (verbose):
PR #1292 already added defaults for
method: Literalfields on request and notification types - could do the same thing here.Related
AI Disclaimer