aaron-bond

commit sha b0ede0b0fa9cd87afb2aca9fbb04136d57537688

Correcting engine version

push time in a month

commit sha 6cc1246c5484f0ad2f080c5cbd54590e41c63438

Updating version information

Can you include a TODO outline to this extension?

push time in a month

PR closed aaron-bond/better-comments

Add FIXME and HACK to default tags

I think these are sane defaults

+18 -0

1 commit in aaron-bond/better-comments/tree/master

7 comments

2 changed files

arvigeus

pr closed time in a month

issue commentaaron-bond/better-comments

I made the decision not to add this to the extension - given that each user can configure their own comment formats to highlight, it's something that would be far too comprehensive to add in here.

GitMensch

comment created time in a month

PR closed aaron-bond/better-comments

Bright script and xml support

+34 -24

4 commit in chrisdp/better-comments/tree/brightScript-and-xml-support aaron-bond/better-comments/tree/master

2 comments

2 changed files

chrisdp

pr closed time in a month

pull request commentaaron-bond/better-comments

Bright script and xml support

Brought these in here https://github.com/aaron-bond/better-comments/commit/db2b4a940918177d41214ee04be9e4c9f558abba

chrisdp

comment created time in a month

commit sha db2b4a940918177d41214ee04be9e4c9f558abba

adding xml and brightscript support

push time in a month

commit sha fdce6b84ef893dd90d1d636581fc3852561658cc

updating changelog

Feature Request: language extension additions

push time in a month

issue commentaaron-bond/better-comments

What I meant is you can change the language mode to whatever you want - HTML in this case. Have you tried that?

lau-a

comment created time in a month

issue closedaaron-bond/better-comments

Can you include a TODO outline to this extension?

Similar to https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.todo-tree, just without the need to use another comment extension...

closed time in a month

GitMensch

issue commentaaron-bond/better-comments

Can you include a TODO outline to this extension?

I made the decision not to add this to the extension - given that each user can configure their own comment formats to highlight, it's something that would be far too comprehensive to add in here.

GitMensch

comment created time in a month

issue closedaaron-bond/better-comments

Needs "better comments" summary for opened folder/workspace

Pretty much like PROBLEMS window, there should be a specific tab for COMMENTS (much like a TODO list) Screenshot from 2020-03-04 12-32-52

closed time in a month

Pra3t0r5

issue commentaaron-bond/better-comments

Needs "better comments" summary for opened folder/workspace

I made the decision not to add this to the extension - given that each user can configure their own comment formats to highlight, it's something that would be far too comprehensive to add in here.

Pra3t0r5

comment created time in a month

issue closedaaron-bond/better-comments

[Feature Request] Add list style ToDo along side X

For the Todo lists I offer to add a new microsyntax like this:

// TODO Create subsequent Person, RealPerson, Teacher and Student records // [x] ~~Create Person~~ // [ ] Create RealPerson // [ ] Create Teacher // [ ] Create Student

then the Create Person item will be Strike-through and the other came just like TODO style or a bit different.

closed time in a month

Hamcker

issue commentaaron-bond/better-comments

[Feature Request] Add list style ToDo along side X

You can add this to your own configuration in the settings. I actually think this is pretty cool, but it's not something I'd add to the defaults

Hamcker

comment created time in a month

issue closedaaron-bond/better-comments

Feature Request. Is there a way to list all the questions, warning and TODOs all accross the project, similar to TODO Tree

closed time in a month

vibhanshu909

issue commentaaron-bond/better-comments

Feature Request. Is there a way to list all the questions, warning and TODOs all accross the project, similar to TODO Tree

I made the decision not to add this to the extension - given that each user can configure their own comment formats to highlight, it's something that would be far too comprehensive to add in here.

vibhanshu909

comment created time in a month

issue closedaaron-bond/better-comments

Color spans until end-of-line, not end-of-comment

Simple example:

In cases where there is

{
/*! safari */ -webkit-whatever: unset;
/*! IE */ -ms-whatever: unset;
/*! FF */ -moz-whatever: unset;
}

... it kills all styling on the lines

closed time in a month

BananaAcid

issue commentaaron-bond/better-comments

Color spans until end-of-line, not end-of-comment

Tracking via https://github.com/aaron-bond/better-comments/issues/233

BananaAcid

comment created time in a month

issue closedaaron-bond/better-comments

Single line c-style comments aren't styled

example:

// this won't be styled
/* TODO: */
// this will be styled
/*
TODO 
*/

closed time in a month

djbaumann

issue commentaaron-bond/better-comments

Single line c-style comments aren't styled

Tracking via https://github.com/aaron-bond/better-comments/issues/256

djbaumann

comment created time in a month

issue openedaaron-bond/better-comments

Single line block comments don't work as expected

Across multiple languages, having a block comment on a single line causes unintented highlighting (or no highlighting at all).

For example:

This is caused by the way some of the comment delimiters are set up in the code and the way the regex finds block comments.

This bug tracks the following: https://github.com/aaron-bond/better-comments/issues/119 https://github.com/aaron-bond/better-comments/issues/233

created time in a month

issue closedaaron-bond/better-comments

Highlighting not supported on single quote Python docstrings

Screen Shot 2019-05-08 at 12 46 46 PM

As shown above, if the first line is a TODO comment, for some reason it is not highlighted in the editor. If I push the comments down one line (e.g. so that the first comment is on line 2), then it highlights as usual.

closed time in a month

jadchaar

issue commentaaron-bond/better-comments

Highlighting not supported on single quote Python docstrings

Closing this out as I've no reasonable alternative here without ballooning the scope of the regex. Will keep it in mind if any future requests come in

jadchaar

comment created time in a month

issue closedaaron-bond/better-comments

Feature request: Add support for html comment()

It will be very nice if this tool could highlight the html Todo comment.

closed time in a month

ylzsmallsun

issue closedaaron-bond/better-comments

Comments in HTML script tag don't highlight

I'm finding that comments in a <script> tag in an HTML file are not highlighting 😢

Screen Shot 2019-09-05 at 11 35 40 AM

Thanks for making this extension, love it.

closed time in a month

tetondev

issue closedaaron-bond/better-comments

Better Comments is not working in SASS

In the documentation for the better comments extension for VS Code, it states that better comments works with both SCSS and SASS. However, this is not the case currently. Currently, better comments is not working in SASS files but it is working in SCSS files. This is very frustrating as the documentation is telling you something different than what it actually does. Please, would you fix the support for comments in SASS, both silent (// text here) and loud comments (/* text here*/). It is really frustrating not to be able to use better comments in SASS and might be a reason for me to uninstall it if the problem is not fixed soon. Please try and fix support for SASS comments as soon as possible as it would be a good reason for me to not recommend this extension if it is not fixed soon. Thanks.

Screen Shot 2020-03-01 at 10 57 49 AM

closed time in a month

MrDogeBro

commit sha 7decffb8ac08c92c9bdfc2a9e766d5937adf0168

Fixing SASS support, closes #215, closes #123

sass file extension not supported

push time in a month

issue closedaaron-bond/better-comments

sass is mentioned in the list on the read me but is not in the code (scss only).

closed time in a month

ncodefun

issue closedaaron-bond/better-comments

Regular multiline comments where each line starts with asterisk parse incorrectly

When you have a C style multiline comment where each line starts with an asterisk, the comment is parsed as if each line were a highlight. This does not happen when doc style multiline comments (/**) are used.

Example:

/*
* this isn't supposed to be highlighted
* ? This is a question but is not marked as such
*/

/**
* this isn't supposed to be highlighted
* ? This is a question but is not marked as such
*/

Screenshot from 2019-08-04 09-54-42

closed time in a month

matter123

issue closedaaron-bond/better-comments

Specify in documentation that multiline comments require extra asterisk

Expected Multi-line comments triggerd by /* are colorized like the rest.

Actual Only multi-line comments starting with /** are colorized.

FIX CI -> Stack overflow is our best friend -> link to the fix

New features in response to #50

add them as boolean
fontWeight not added because fontWeight accepts a string while the css doc await for a number. I don't want to include misleading options (property could be "bold", "700" but not 700) , better to keep a boolean than introduce complicated usage.
fontFamily and fontSize not availables in VSCode doc

+62 -11

4 commit in Fr33maan/better-comments/tree/feat/bold-italic-underline aaron-bond/better-comments/tree/master

7 comments

4 changed files

Fr33maan

pr closed time in a month

pull request commentaaron-bond/better-comments

merged in here https://github.com/aaron-bond/better-comments/commit/e41ccc42252399423db8ebf7bacc7a36422bed7f Thanks for this. Will get a couple more features added and release a version this week :)

Fr33maan

comment created time in a month

commit sha e41ccc42252399423db8ebf7bacc7a36422bed7f

Pr/253 (#255) * FEAT - add underline/bold/italic to tags In response to https://github.com/aaron-bond/better-comments/issues/50 * FIX - CI is now working Co-authored-by: Fr33maan <[email protected]> Co-authored-by: Fr33maan <[email protected]>

push time in a month

PR merged aaron-bond/better-comments

Pr/253

+64 -12

6 commit in aaron-bond/better-comments/tree/pr/253 aaron-bond/better-comments/tree/master

0 comment

4 changed files

aaron-bond

pr closed time in a month

PR opened aaron-bond/better-comments

Pr/253

+64 -12

6 commit in aaron-bond/better-comments/tree/pr/253 aaron-bond/better-comments/tree/master

0 comment

4 changed files

pr created time in a month

create barnchaaron-bond/better-comments

branch : pr/253

created branch time in a month

pull request commentaaron-bond/better-comments

It occurs to me that there's no technical limitation to make these mutually-exclusive. So I'm making some changes to the PR unless you've objections?

Fr33maan

comment created time in a month

pull request commentaaron-bond/better-comments

It's OK, you've convinced me. I'm testing this at the minute and assuming it's all good I'll merge today. Thanks :)

Fr33maan

comment created time in a month

commit sha b44ad59d84f8955fae9e14fcc0dd38f772685ea5

Updating package lock

commit sha 1365e4da6e87d9a880830c35f55168b127d2a346

reverting to tabs temporarily

push time in a month

commit sha 26c16cd4808f60313870e74e5ca150aebacbdd99

Updating package to latest versions

push time in a month

pull request commentaaron-bond/better-comments

Unexpected whitespace color.

Thanks for this. I really like the bold/italic changes. I'm updating the vscode version too, so that should fix the issue with the typings.

I'm a little worried about introducing mutually-exclusive settings though re. the underline / strikethrough. That feels like something that'll get a lot of complaints. Is underline something you need?

Fr33maan

comment created time in a month

issue commentaaron-bond/better-comments

I've never heard anything back on my SO questions or other attempts to find a resolution to this.

I've raised a feature request here: https://github.com/microsoft/vscode/issues/102390

dingyi1993

comment created time in a month

issue openedmicrosoft/vscode

Add the option to exclude whitespace characters from setDecoration

I manage the Better Comments extension and an issue that has come up a few times is that users would like to be able to have the color styles applied to text only within comments; not the whitespace.

Here, I have a styles applied changing the comment colors:

Rather than having whitespace characters go red/blue/green here, it would be nice to be able to exclude those and leave them as-is.

Thanks!

created time in a month

Thank you kindly @stephenhaunts

aaron-bond

comment created time in a month

Adding ContainsProfanity method

My PR has been merged already; the method is ContainsProfanity. I think @stephenhaunts is planning to release the nuget package with the update.

aaron-bond

comment created time in a month

pull request commentstephenhaunts/ProfanityDetector

@stephenhaunts thanks for bringing this in :) much appreciated. If you don't mind, please give me a heads-up when this is expected in Nuget. Thanks!

aaron-bond

comment created time in a month

pull request commentstephenhaunts/ProfanityDetector

Adding ContainsProfanity method

@stephenhaunts let me know if there's a more appropriate name for the method

aaron-bond

comment created time in a month

PR opened stephenhaunts/ProfanityDetector

Adding ContainsProfanity method

The Contains Profanity method will allow for incidences Scunthorpe being caught.

With a bit more time I think I'd like to profile the performance of the method but it appears to run pretty quick in my tests so far.

+111 -24

2 commit in aaron-bond/ProfanityDetector/tree/main stephenhaunts/ProfanityDetector/tree/main

0 comment

3 changed files

pr created time in a month

push eventaaron-bond/ProfanityDetector

commit sha f0540c1b5f8e3f5b6c1fcff3b0c9944553b18a58

Updating Interface to match changes

push time in a month

push eventaaron-bond/ProfanityDetector

commit sha f052c43833ec6ae092ae40ddac0479f85caeb471

Adding ContainsProfanity method and some tests

push time in a month

fork aaron-bond/ProfanityDetector

This is a simple library for detecting profanities within a text string.

stephenhaunts/ProfanityDetector aaron-bond/ProfanityDetector

fork in a month

In my case it's a tool that generates random Ids for users; I don't want to end up with ass123 accidentally so this tool can give me a retry case.

aaron-bond

comment created time in a month

@stephenhaunts if it's not something the package already does, would you be open to a PR with a new public method specifically to find cases like Scunthorpe?

aaron-bond

comment created time in a month

@stephenhaunts yep, exactly. Is that a thing?

aaron-bond

comment created time in a month

issue openedstephenhaunts/ProfanityDetector