-
- [x] Frontend routes contains wildcard variables written in `camelCase`
- [ ] Correctly formatted
- [x] Routes are displayed with `inline coding text` (backticks)
-
**Version Used**: .NET 6.0.100
**Steps to Reproduce**:
1. Editor Config from .NET 6 `dotnet new editorconfig`
1. Define something like
`private static Lazy s_lazyConverters = new( ... )`
…
-
**Vulnerabilities**
DepShield reports that this application's usage of [lodash.camelcase:4.3.0](https://ossindex.sonatype.org/component/pkg:npm/lodash.camelcase@4.3.0) results in the following vulner…
-
#### Bug Report Checklist
- [X] Have you provided a full/minimal spec to reproduce the issue?
- [X] Have you validated the input using an OpenAPI validator ([example](https://apidevtools.org/swagg…
-
html attributes are always lower case, hence why they tend to kebab-case, so you can tell the words apart. If you stick a camelCase prop on a web-component tag in react, it gets forced to lowercase, a…
-
https://developers.google.com/protocol-buffers/docs/style specifies naming conventions:
> Use CamelCase (with an initial capital) for message names – for example, SongServerRequest.
> Use under…
-
Tehnicki mozes i ovako, ali nije praksa da se koristi "first name" kao ime varijable, ili da pocnes sa "1.5". Ako ti vec te varijable trebaju, koriati deskriptivno, pa se odluchi za camelCase ili snak…
-
Ensure widget IDs are formatted in `camelCase`
**Good**
btnSubmit
**Bad**
btn_submit
-
Please comment for new proposals of SFTI's naming conventions concerning the openAPI action / redocly workflow
-
as of v0.014, still only handles 64bit double-floats. It would be nice to also handle 32bit single-floats and 128bit floats ("quad"?).
pryrt updated
8 years ago