question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pipe naming convention is not explicitly described

See original GitHub issue

📚 Docs or angular.io bug report

Description

It is not currently clear in the documentation how to name pipes.

🔬 Minimal Reproduction

What’s the affected URL?

https://angular.io/guide/styleguide#style-02-09

Reproduction Steps

Naming and using a pipe with the name “my-pipe” will cause issues at runtime. This is the case for any pipe whose name property is written in kebab case.

Expected vs Actual Behavior

I would expect that the documentation explicitly state that camel case is the proper format for pipes. Currently, the example shown is given in camel case, however, there is nothing stating that kebab case is invalid.

📷Screenshot

image

🔥 Exception or Error


Template parse errors:
Parser Error: Unexpected token '-' at

See here for reproduction: https://stackblitz.com/edit/angular-issue-pipe-with-dash

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
Airbladercommented, Jul 22, 2019

I think this should either be made to work or it should be a compile time error.

0reactions
angular-automatic-lock-bot[bot]commented, Sep 28, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Angular coding style guide
Looking for an opinionated guide to Angular syntax, conventions, and application structure? Step right in. This style guide presents preferred conventions ...
Read more >
Naming Conventions: Why You Need Them for Clean Data
Naming conventions in data analytics are rules devised by data analysts to clearly identify and categorize the completion of “events” with your product...
Read more >
PEP 423 – Naming conventions and recipes related to ...
It is explicit: when one sees project name, he guesses package/module name, and vice versa. It also limits implicit clashes between package/ ...
Read more >
TM1 Object Naming Conventions - IBM
Object names in TM1 rules​​ This guideline protects you if the objects or elements ever become part of a rule statement where those...
Read more >
PEP 8: The Style Guide for Python Code
Please see the companion informational PEP describing style guidelines for the C code ... This PEP takes no explicit position on how (or...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found