Morning @abyszuk,

I imagine the fix would be the maximum allowed in a <=?

For example the following code snippet:

cic_proc_p        : process(all)

if the whitespace rule was configured for number_of_spaces: <= 2 the result would be:

cic_proc_p  : process(all)

two spaces before the colon?

--Jeremy

Yes, that's my thought as well.

Afternoon @abyszuk ,

I pushed an update for this to the issue-1190 branch. When you get a chance could you check it out on your end and let me know if it works for you?

Thanks,

--Jeremy

Hello @jeremiah-c-leary
I've tested the fix on my end and I can confirm it works as intended.
It works partially. For number_of_spaces: <=1

• works OK if number of spaces is > 1
• works OK if number of spaces = 1
• returns an error if number of spaces is 0 ( main_p: process(clk_i)
process_024 | Error | 142 | Add 1 space(s) between main_p and :

Thank you for the fast update!

After a bit of debugging the problem seems to be that if there's no space then in the Rule._analyze() method the self.analyze_no_whitespace_token() method is called instead of self.analyze_whitespace_token()

Evening @abyszuk ,

I pushed an update to the no spaces case. Essentially if there are no spaces then the <=1 should always pass. Let me know if there are any other issues.

Thanks,

--Jeremy

Yes, I can confirm this works properly now.
Again, thank you for the fast update and great work!

Awesome, I will get this merged to master.

Again, thank you for the fast update and great work!

Thanks for the kind words.

--Jeremy