Juho Vepsäläinen

1. I was thinking of adding an explicit note (a tip?) mentioning about it if/when it's relevant. 2. I think the point is to be more explicit about it. The...

2. seems more valuable. 1. is likely a warning here and there. Suggesting different paths to read is a good idea.

@shadowz10 It's a bit too early as we have to finalize the book. I set up #79 for tracking.

@epoberezkin uses it internally MailOnline.

Correct. It's something for organizations that want to ensure people provide the right meta information for projects for example.

It's not a mainstream idea yet. We can leave the issue open for now and decide later. It's not primary content for sure.

>>Most likely it would be nice to discuss how it works with multiple people and different roles. > Any ideas for that? The key here might be to look into...

> Would you like to add that? Sure. I can add a few examples. Later on these could grow into case studies if there's time/interest towards that.

Yeah, I think it would be something we would provide for paying readers as bonus content. I have some ideas on how to approach this.

Yeah, TSLint should go away and we should extend the TypeScript bits with notes on ESLint and how it goes together with it.