-
Notifications
You must be signed in to change notification settings - Fork 470
- #3050 · jasonbahl opened
on Feb 20, 2024 2
Issues
is:issue state:open
is:issue state:open
Issue creation is restricted in this repository
Search results
Deprecated
ancestors/parentconnections on non-hierarchical post types produce an invalid schema (edgenode/cursordeprecated, butEdgeinterface is not)component: connectionsRelating to GraphQL ConnectionsRelating to GraphQL Connectionscomponent: interfacesRelating to GraphQL Interface TypesRelating to GraphQL Interface Typeseffort: lowAround a day or lessAround a day or lesshas: workaroundA temporary workaround has been providedA temporary workaround has been providedimpact: medMinor performance improvements, fix broad user base issuesMinor performance improvements, fix broad user base issueslang: phpPull requests that update PHP codePull requests that update PHP codestatus: actionableReady for work to beginReady for work to begintype: bugIssue that causes incorrect or unexpected behaviorIssue that causes incorrect or unexpected behaviorStatus: Open.#3979 In wp-graphql/wp-graphql;spike: evaluate Automattic's pressship for Plugin Check coverage and the WP.org release tail
needs: discussionRequires a discussion to proceedRequires a discussion to proceedscope: build scriptsAutomating task runners and compilation processesAutomating task runners and compilation processestype: spike 🏐An issue that needs more research before becoming actionableAn issue that needs more research before becoming actionableStatus: Open.#3963 In wp-graphql/wp-graphql;Phase 3: oneOf polymorphic mutation inputs (unified content creation + relationship management)
component: inputRelating to GraphQL Input TypesRelating to GraphQL Input Typescomponent: mutationsRelating to GraphQL MutationsRelating to GraphQL Mutationseffort: highMore than a weekMore than a weekimpact: medMinor performance improvements, fix broad user base issuesMinor performance improvements, fix broad user base issuesneeds: discussionRequires a discussion to proceedRequires a discussion to proceedscope: apiIssues related to access functions, actions, and filtersIssues related to access functions, actions, and filterstype: featureNew functionality being addedNew functionality being addedStatus: Open.#3951 In wp-graphql/wp-graphql;🔬 Spike: mapping Gutenberg Blocks to the WPGraphQL Schema
component: architectureRelating to fundamental architectural decisionsRelating to fundamental architectural decisionseffort: highMore than a weekMore than a weekimpact: highUnblocks new use cases, substantial improvement to existing feature, fixes a major bugUnblocks new use cases, substantial improvement to existing feature, fixes a major bugneeds: discussionRequires a discussion to proceedRequires a discussion to proceedscope: apiIssues related to access functions, actions, and filtersIssues related to access functions, actions, and filterstype: spike 🏐An issue that needs more research before becoming actionableAn issue that needs more research before becoming actionableStatus: Open.#3950 In wp-graphql/wp-graphql;🎯 Tracking: content and excerpt output formatting controls (plain-text format + excerpt opt-out)
component: model layerRelating to the Model LayerRelating to the Model Layereffort: medLess than a weekLess than a weekimpact: medMinor performance improvements, fix broad user base issuesMinor performance improvements, fix broad user base issuesneeds: discussionRequires a discussion to proceedRequires a discussion to proceedobject type: postRelating to the Post Object TypesRelating to the Post Object Typesstatus: actionableReady for work to beginReady for work to begintype: featureNew functionality being addedNew functionality being addedStatus: Open.#3949 In wp-graphql/wp-graphql;Extensions page: Install & Activate flows surface multiple errors (array_map fatal, plugin not found, invalid JSON, plugin file does not exist)
effort: medLess than a weekLess than a weekimpact: medMinor performance improvements, fix broad user base issuesMinor performance improvements, fix broad user base issuesneeds: reproductionThis issue needs to be reproduced independentlyThis issue needs to be reproduced independentlyscope: extensionsIntegrating plugins, add-ons, or other extensionsIntegrating plugins, add-ons, or other extensionstype: bugIssue that causes incorrect or unexpected behaviorIssue that causes incorrect or unexpected behaviorStatus: Open.#3934 In wp-graphql/wp-graphql;ContentNode should represent public, URI-addressable content; utility post types should not implement it
compat: breaking changeThis is a breaking change to existing functionalityThis is a breaking change to existing functionalitycomponent: architectureRelating to fundamental architectural decisionsRelating to fundamental architectural decisionscomponent: connectionsRelating to GraphQL ConnectionsRelating to GraphQL Connectionscomponent: interfacesRelating to GraphQL Interface TypesRelating to GraphQL Interface Typeseffort: highMore than a weekMore than a weekimpact: medMinor performance improvements, fix broad user base issuesMinor performance improvements, fix broad user base issuesneeds: discussionRequires a discussion to proceedRequires a discussion to proceedscope: performanceEnhancing speed and efficiencyEnhancing speed and efficiencytype: featureNew functionality being addedNew functionality being addedv3.0Features / Bugs intended to be worked on as part of a v3.0 releaseFeatures / Bugs intended to be worked on as part of a v3.0 releaseStatus: Open.#3932 In wp-graphql/wp-graphql;🎯 Tracking: mapping WordPress data registries (settings, meta, options) to the WPGraphQL Schema
component: architectureRelating to fundamental architectural decisionsRelating to fundamental architectural decisionseffort: highMore than a weekMore than a weekimpact: highUnblocks new use cases, substantial improvement to existing feature, fixes a major bugUnblocks new use cases, substantial improvement to existing feature, fixes a major bugneeds: discussionRequires a discussion to proceedRequires a discussion to proceedscope: apiIssues related to access functions, actions, and filtersIssues related to access functions, actions, and filterstype: featureNew functionality being addedNew functionality being addedStatus: Open.#3931 In wp-graphql/wp-graphql;spike:
register_graphql_argument(), arguments that carry their own resolution behaviorcomponent: architectureRelating to fundamental architectural decisionsRelating to fundamental architectural decisionseffort: medLess than a weekLess than a weekimpact: medMinor performance improvements, fix broad user base issuesMinor performance improvements, fix broad user base issuesneeds: discussionRequires a discussion to proceedRequires a discussion to proceedscope: apiIssues related to access functions, actions, and filtersIssues related to access functions, actions, and filterstype: spike 🏐An issue that needs more research before becoming actionableAn issue that needs more research before becoming actionableStatus: Open.#3930 In wp-graphql/wp-graphql;🎯 Tracking: contract test coverage for WPGraphQL actions and filters
effort: highMore than a weekMore than a weekhelp wantedIssue with a clear description that the community can help withIssue with a clear description that the community can help withimpact: medMinor performance improvements, fix broad user base issuesMinor performance improvements, fix broad user base issuesscope: testsDeveloping unit tests, integration tests, and ensuring coverageDeveloping unit tests, integration tests, and ensuring coveragestatus: actionableReady for work to beginReady for work to begintype: choreMaintenance tasks, refactoring, and other non-functional changesMaintenance tasks, refactoring, and other non-functional changesStatus: Open.#3929 In wp-graphql/wp-graphql;Publish a PHP / WordPress minimum-version support policy (and ship an advance deprecation warning)
effort: medLess than a weekLess than a weekimpact: highUnblocks new use cases, substantial improvement to existing feature, fixes a major bugUnblocks new use cases, substantial improvement to existing feature, fixes a major bugneeds: discussionRequires a discussion to proceedRequires a discussion to proceedscope: docsUpdating, correcting, and improving documentationUpdating, correcting, and improving documentationtype: enhancementImprovements to existing functionalityImprovements to existing functionalityStatus: Open.#3925 In wp-graphql/wp-graphql;spike: assess upgrading webonyx/graphql-php to v16
needs: discussionRequires a discussion to proceedRequires a discussion to proceedscope: dependenciesManaging, updating, or removing dependenciesManaging, updating, or removing dependenciestype: spike 🏐An issue that needs more research before becoming actionableAn issue that needs more research before becoming actionableStatus: Open.#3923 In wp-graphql/wp-graphql;