beman.exemplar: change library status to under development (exemplar is a template library)

[neatudarius]

Issues: bemanproject/beman#77

Expected README.md:

[neatudarius]

@wusatosi , what should I do here?

I didn't change these lines. And I want to keep them! (collapsable menus in docs).

[wusatosi]

@wusatosi , what should I do here?

I didn't change these lines. And I want to keep them! (collapsable menus in docs).

Hum, weird, inline HTML check should have been disabled. I will look into this.

[neatudarius]

@wusatosi , what should I do here?

I didn't change these lines. And I want to keep them! (collapsable menus in docs).

Hum, weird, inline HTML check should have been disabled. I will look into this.

OK. Then I will proceed with the PR, as this behaviour is not from changed lines.

[RaduNichita]

LGTM!

[wusatosi]

Is there a reason to use <img> html tag instead of markdown facility here?

markdown lint automatically ignore line length caused by urls, ideally ignore would not be needed here.

Also, can we put this two in separate lines?

[wusatosi]

According to markdown-lint documentation.

Enable all rules: <!-- markdownlint-enable -->

This will cause the previously configured ignore rule to be flushed out.

Is there a reason we need to use this disable-enable pair?

If a ignore have to be used, consider: <!-- markdownlint-disable-next-line -->.

If ignore have to be multi-line, use the idiom suggested by markdownlint's documentation:

<!-- markdownlint-disable -->
any violations you want
<!-- markdownlint-restore -->

[wusatosi]

Why not simply do:

Suggested change

	<!-- markdownlint-disable -->
	<img src="https://github.com/bemanproject/beman/blob/main/images/logos/beman_logo-beman_library_under_development.png" style="width:5%; height:auto;"> 
	<!-- markdownlint-enable -->
	
	

[neatudarius]

Second syntax for including image doest not allow resize, at least not in standard Markdown on GitHub. You can simulate a change by editing a file in UI and do preview.

[wusatosi]

OK. Then I will proceed with the PR, as this behaviour is not from changed lines.

No. lint break is caused by changed lines.

Avoid fighting with markdownlint with ignore statements, ignore should be the last resort.

Put faith into the linting infrastructure, let's not have our code littered with lint-ignores.

[neatudarius]

OK. Then I will proceed with the PR, as this behaviour is not from changed lines.

No. lint break is caused by changed lines.

Avoid fighting with markdownlint with ignore statements, ignore should be the last resort.

Put faith into the linting infrastructure, let's not have our code littered with lint-ignores.

I agree with any solution which can work right now. So what should I do if the CI complains the line is too long? And I actually want to insert a text with hyperlink? (The text is short, the hyperlink is long).

Currently, the infrastructure seems to not consider this case. If this is true, it should be solved in other issue/PR.

[JeffGarland]

Overall this look good.

[wusatosi]

OK. Then I will proceed with the PR, as this behaviour is not from changed lines.

No. lint break is caused by changed lines.
Avoid fighting with markdownlint with ignore statements, ignore should be the last resort.
Put faith into the linting infrastructure, let's not have our code littered with lint-ignores.

I agree with any solution which can work right now. So what should I do if the CI complains the line is too long? And I actually want to insert a text with hyperlink? (The text is short, the hyperlink is long).

Currently, the infrastructure seems to not consider this case. If this is true, it should be solved in other issue/PR.

It looks like markdown lint ignores length overflow due to url via []().

[neatudarius]

It looks like markdown lint ignores length overflow due to url via []().

@wusatosi , would you agree with current PR state? Check rendered version.