-
# Frontend Routes
- [ ] Frontend routes contains wildcard variables written in `camelCase`
- [ ] Correctly formatted
- [ ] Routes are displayed with `inline coding text` (backticks)
-
I have a module namespace called `X86_64` which represents the x86-64 architecture. `rubocop` seems to think this module/class name should be written in CamelCase. This is of course impossible, becaus…
-
- [ ] Frontend routes contains wildcard variables written in `camelCase`
- [ ] Correctly formatted
- [ ] Routes are displayed with `inline coding text` (backticks)
## Comments
-
Elect one naming convention for your tests cases and stick to it.
You have both ```CamelCases``` and ```underscore_namings```
-
Is this expected behaviour? (running v1.2.0)
```
In[1]: camel_to_underscore("emailOn_POS")
Out[1]: 'email_on_po_s'
```
I expected `email_on_pos`.
Note that the input string is the result of …
-
`_ERC20ToSdkCoin_ConvertAmount` and `_SdkCoinToERC20_ConvertAmount` should be in camelCase format to account for standards used in libraries. So change to the name to `convertAmountERC20ToSdkCoin` an…
-
Today after a deployment we take all of the outputs the bicep module we deploy and add them to the `.env` file (and for .NET apps, we add them to the .NET Secret Store as well).
Since environment v…
-
New Feature
```rust
//Rust side
extern "Rust" {
fn get_value()->i16;
}
```
```rust
//build.rs
use std::path::PathBuf;
fn main() {
let out_dir = PathBuf::from("./generated…
-
- [x] Frontend routes contains wildcard variables written in camelCase
- [ ] Correctly formatted
- [x] Routes are displayed with inline coding text (backticks)
-
**Version Used**:
Version 16.9.0 Preview 3.0 [30904.5.main]
**Steps to Reproduce**:
```C#
class Program
{
static (int a, int b) s_field; // invoke convert tuple to type her…