Closed slide closed 1 year ago
This looks good. I like the idea of using **kwargs instead of a long list of possible arguments.
Because we do periodic releases, we would like to merge this pull request into another branch. Can you change the target branch from master to case_insensitive_naming? Then when we merge our changes to master and do a release, we will include this updated functionality for case insensitive naming.
Done, thanks!
@slide have you written any unit tests for this? Also, have you tested it with composing out a netlist?
No, I have not. I left the company that I was doing this for and don't really have a way to continue working on it. Feel free to revert if its not something you think is good.
This is in regards to #116, I had a similar issue where there were components with the same name, but different casing and so I got an error. This adds a possible way to have a flag to use case insensitive name matching. I am not sure if this implementation is something the project would be willing to accept, it does work for me. I am definitely willing to work on a different implementation to get this feature included.