You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We want to use TypeScript to get more type safety and earlier error detection. Therefore, if possible, we should not use the type “any” in declarations.
Describe the solution you'd like
First, we can introduce a DomainStory as a type (interface), for example. The DomainStory contains an array of BusinessObject as properties, a string that holds the 'Info', and a string that holds the 'Version'.
Next, the import can be adjusted. This means that the DomainStory is filled with the data from the import and used accordingly. We have to keep in mind that older exported version should also work here.
Afterwards, the export can be adjusted.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
DanielHeckert
changed the title
Implement a DomainStory model to improve the typing of parameters
Implement a DomainStory model to improve type safety
Sep 26, 2024
Is your feature request related to a problem? Please describe.
We want to use TypeScript to get more type safety and earlier error detection. Therefore, if possible, we should not use the type “any” in declarations.
Describe the solution you'd like
First, we can introduce a DomainStory as a type (interface), for example. The DomainStory contains an array of BusinessObject as properties, a string that holds the 'Info', and a string that holds the 'Version'.
export interface DomainStory {
businessObjects: BusinessObject[],
info: string,
version: string
}
Next, the import can be adjusted. This means that the DomainStory is filled with the data from the import and used accordingly. We have to keep in mind that older exported version should also work here.
Afterwards, the export can be adjusted.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: