Comments (5)
Evening @Benito-E ,
I would agree the inclusion of multiple local rules would be helpful. That feature has not received any attention from it's inception as I think you are the only person who has actually used it.
I can allow multiple local rules, similar to configurations, and also change the local_rules
option in the configuration files to a list.
I could also allow for one level of nesting similar to how VSG organizes it's rules.
Would you have a preference for either method?
--Jeremy
from vhdl-style-guide.
Hi again @jeremiah-c-leary,
While I have a preference for the former of the two methods, I also believe both methods would be valuable. The latter of the two methods would be useful even simply for organizing large sets of local rules, and the former of the two methods would be useful for collaboration, if multiple developers had separate sets of local rules that could be mixed and combined; or perhaps if a particular project had an overarching set of rules that all developers were meant to use, and each individual developer was allowed to develop their own set of rules.
The only reason I have a preference for the former of the two methods is because it would theoretically allow for the flexibility to accomplish the both methods: you could accomplish the latter method by having an external script that scanned a directory for directories and passed those names to VSG's --local_rules
option.
In any case, I appreciate the enthusiasm and support you have for this project!
-- Benito
from vhdl-style-guide.
Evening @Benito-E ,
I would agree the former method, allowing multiple local rules via --local_rules
, would be the easier of the two methods. One problem I could see with multiple local rules would be with rule id collision. If multiple rules had the same id then it could be difficult to determine which one actually failed. I do not believe this issue goes away with the later method. I suppose the conflicts would need to be managed outside of VSG.
Is this a feature you would like to see implemented or is it a feature that can be deferred. I ask because you are the first person who has asked about local rules in the 6 years I have been developing VSG. I originally added it so others could write their own rules, but I suspect you are the only person who has. I would rather postpone the implementation of this feature if there is no demand for it. Hopefully that makes sense.
In any case, I appreciate the enthusiasm and support you have for this project!
Thanks for the kind words. It is nice to know my efforts are appreciated.
Regards,
--Jeremy
from vhdl-style-guide.
Morning @jeremiah-c-leary,
I would rather postpone the implementation of this feature if there is no demand for it. Hopefully that makes sense.
No worries at all, that makes perfect sense! I appreciate the consideration and thought regardless, and if you do decide to implement this feature I'll simply be glad to have contributed to that outcome.
Sincerely,
--Benito
from vhdl-style-guide.
Evening @Benito-E ,
If it is okay with you then I will make this a deferred issue. In that way the idea will be documented and if you or someone else would like the feature implemented then the issue can be pulled into development.
Regards,
--Jeremy
from vhdl-style-guide.
Related Issues (20)
- IndexError: pop from empty list when having lots of parenthesis in a package body HOT 6
- Extended configurability HOT 16
- Rule for "space around operators" (?) HOT 8
- Local Rule Creation Documentation HOT 5
- Rule for new lines between end of generic map and port map HOT 5
- Prefix/suffix exceptions not exempted from case checking in instantiation_008 HOT 6
- Rule concerning label presence after end keyword on component declaration HOT 4
- PascalCase/camelCase and acronyms HOT 9
- Options for merging config files HOT 1
- Forcing single space when disabling alignment rules HOT 6
- record element is incorrectly recognized as type element HOT 1
- Comment tricks vsg into incorrect parsing state HOT 3
- Better diagnostics when local indent rules don't match default config HOT 4
- Whitespace rules should allow <= operator HOT 8
- Ignore Components for port rules HOT 4
- Function/Procedure name as optional in end statement HOT 6
- Regex case rule fails on port_map_002 HOT 3
- Unable to have a series of port, port map declarations, signal declarations all be aligned even across comments or white space HOT 3
- Add Pascal_Snake_Case to case checking rules HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vhdl-style-guide.