luigidemasi opened a new issue, #198:
URL: https://github.com/apache/camel-kit/issues/198

   ## Description
   
   The shared graph enums currently include Mule and BizTalk node and 
relationship types. This makes every new migration a change to core and couples 
graph loading to the set of installed types. Let packs own their type 
definitions and Java adapters while core stores and traverses generic graph 
records. [Node 
types](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/kit/camel-kit-graph/src/main/java/org/apache/camel/kit/graph/model/NodeType.java)
 · [Graph 
serialization](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/kit/camel-kit-graph/src/main/java/org/apache/camel/kit/graph/GraphSerializer.java)
 · [BizTalk graph integration 
(#8)](https://github.com/apache/camel-kit/issues/8)
   
   ## Acceptance criteria
   
   - [ ] Use stable namespaced identifiers for contributed node and edge types. 
Each pack owns its schemas, typed adapters, domain rules and mappings for 
existing identifiers. Keep core free of migration-specific type definitions and 
branches.
   - [ ] Verify existing Mule and BizTalk graphs and queries with their packs 
present. Test a new graph type supplied entirely by a fixture pack.
   - [ ] With the provider absent, load, traverse, save and reload an 
unfamiliar record within a supported graph format. Preserve identifiers, 
properties and relationships. Report specialized analysis as unavailable and 
keep a workflow that requires it incomplete.
   - [ ] Reject malformed records and unsupported graph formats with actionable 
errors.
   
   ## Website impact
   
   Required. Explain the graph format, extension registration, legacy 
compatibility and behavior when a provider is missing.
   
   _AI-generated by Codex on behalf of @luigidemasi._
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to