-
The problem Im having is that JAXB doesnt recognize a setter for a property if
the setter parameter is a not exactly of the same as the parameter of the getter
but rather a "parent-class".
for Exampl…
-
#### Is your feature request related to a problem? Please describe.
Following below source code analysis rule, we use private setter on collection properties
The rule is:
https://docs.microsoft.c…
Haihg updated
3 months ago
-
```
It would make SnakeYAML more convenient for Scala users if it could check for
the Scala convention for setters and geaters.
That is, currently to use SnakeYAML with Scala, Scala users must put
…
-
```
It would make SnakeYAML more convenient for Scala users if it could check for
the Scala convention for setters and geaters.
That is, currently to use SnakeYAML with Scala, Scala users must put
…
-
### 🐛 The bug
```
WARN [Vue warn]: Extraneous non-props attributes (data-v-14ce88ff) were passed to component but could not be automatically inherited because component renders fragment or text roo…
-
-
```
It would make SnakeYAML more convenient for Scala users if it could check for
the Scala convention for setters and geaters.
That is, currently to use SnakeYAML with Scala, Scala users must put
…
-
Hello,
I cannot find in the documentation whether value getters and setters are supposed to be non-blocking or not. Looking at the code, it looks like they are indeed supposed to be. And there s…
-
Now, it allows to generate right return type only for 'long' doc blocks, like this:
```php
/**
* Some variable
*
* @var string
*/
private $var;
```
And it generates getter and setter …
-
```
It would make SnakeYAML more convenient for Scala users if it could check for
the Scala convention for setters and geaters.
That is, currently to use SnakeYAML with Scala, Scala users must put
…