Open atedesch1 opened 2 years ago
The issue you're experiencing seems to be related to the specific implementation or version of the library or framework you're using, rather than a fundamental problem with the concept itself. Without more information about the context and the specific library or framework you're using,
However, based on the code snippet you provided, it appears that you're creating a collection with an item and assigning an array of events to the events
field of the item. However, when you print the collection to JSON, the event
field of the item is empty. It's important to note that the Item
class or definition you're using might differ depending on the library or framework.
To troubleshoot this issue, you can consider the following steps:
Ensure that you are using the correct syntax and API calls for your library or framework to define and add events to an item. Consult the documentation or examples provided by the library or framework to verify the correct usage.
Double-check that you are using the latest version of the library or framework, as newer versions might include bug fixes or improvements related to events or collections.
Check if there are any reported issues or discussions related to events in the library or framework's issue tracker or community forums. It's possible that others have encountered similar problems and found workarounds or solutions.
If you're still unable to resolve the issue, consider reaching out to the library or framework's support channels for assistance. They will have the most accurate and up-to-date information about the specific implementation you're using.
@atedesch1
which json file this bug is occur. can you give link @atedesch1
If an Item is created with the field events instead of adding events after the object is created, when you try to run the collection that contains it with newman it doesn't recognize this field and instead the actual object if printed to json has the event field as an empty array.
Example:
When printed to json:
Also, if you add the Item as any and instead of the field events you use event, everything works fine.
The problem is ItemDefinition type has the field events instead of event