The file reader is very simple example of component to read in files. If you have not done so already please have a read of A brief history of Iguana to understand the design philosophy here. This is simple starting component to customize to what you really need.
| Expand | ||
|---|---|---|
| ||
There is only one field to configure - the SourceDir. This is the directory that the component feeds from.  |
...
| Expand | ||
|---|---|---|
| ||
The file matching logic is deliberately isolated in it’s own file which we can see here: https://bitbucket.org/interfaceware/fromfile/src/main/MatchRules.lua Why do we put this logic in it’s own file? It’s applying a concept call Separation of Concerns. We simplify code and make it easy to understand by separating it into its own file. Looking the code you can see that this code will only match files with the extensions hl7, log and txt. If you need to change it then you have a very simple obvious place to go. |
| Expand | ||||
|---|---|---|---|---|
|
| |||
The processing file logic is very straightforward, the source is here: https://bitbucket.org/interfaceware/fromfile/src/main/mainProcessFile.luaIt’s deliberately simple to make the code non intimidating to alter and customize It inhales the file, queues the contents and deletes it. If you want to do something different or more complex - you absolutely can. |
| Expand | ||
|---|---|---|
| ||
You do not have to use the components we supply in production. In fact if you are a large company I would not recommend it. It would make more sense to start with the components we give you. Customize them the way that works for your organization and make your own official git collections. That makes a lot more sense in terms of giving you the control and standardization needed for large organizations. |
| Expand | ||
|---|---|---|
| ||
Reach out! Lets talk about what you need to do. We are here to help. We are genuinely interested in getting a real understanding of the kinds of problems that customers need to solve.There We are a variety of ways we might help you.
looking ways to make our customer’s lives easier, whether that’s through better documentation, examples or just a little friendly encouragement. |
| Expand | ||
|---|---|---|
| ||
In the long run we expect larger customers operating at scale will probably find it benefits them to curate their own ‘standard’ component set. These are components which mean their typical needs based on the needs of their organization. We also expect there will be areas where we develop new components that fit well defined common use cases. Cases that meet the needs of thousands of interfaces. In other cases it will be about helping large companies build components which are ultra well suited to them. |
Hope that helps and do free to reach out and talk with us.