[MGNLGQL-36] Moving whole light module directory won't fire event to update GraphQL definitions in registry Created: 02/Jul/20  Updated: 09/Feb/21  Resolved: 09/Feb/21

Status: Closed
Project: Magnolia GraphQL
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLGQL-60 GraphQL type not registered for a mod... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: GraphQL Phase 1

 Description   

canh.nguyen

During pre-int QA, I found an issue that when I move the whole light modules to another folder then move it back again, it could not create graphql types for book (in my light module has book refer to book category). I have to make some changes to book.yaml to make content type reload then it worked fine.
I think that we need to add some delay to a content type that has reference to another content type.



 Comments   
Comment by Simon Lutz [ 25/Aug/20 ]

Initial investigation showed that issue is rather in MAGNOLIA, not GQL.

Generated at Mon Feb 12 05:51:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.