-
Hello,
please add non-codable property wrapper, as below, for properties that do not support codable protocol or do not want to decode / encode but can still be used and set separately.
``` swift
…
-
크리스마스 연휴라서 좀 늦을수도 있겠네요
godrm updated
2 years ago
-
The `@ParameterStorage` used e.g. in `@QueryParameter` is shared among all instances of one implementation of `Responder`.
Consider the following code:
```swift
import Meridian
import Foundati…
-
**Information**
- Language: Swift
- Plugins: 'none'
**Description**
Some of Swift's keywords are missing. This issue is here for myself to make a collection over the upcoming week, after which I…
-
I haven't made up my mind yet whether it makes sense to expose a Defaults property wrapper or not. Happy to discuss whether it makes and how it would look like.
- https://nshipster.com/propertywrap…
-
I checked that Swift 5 is correctly selected in my target and in pods.
I have correctly configure the development the version in my Podfile:
```
pod 'Resolver', :git => 'https://github.com/hml…
-
### Question
What are the options and thoughts on adding separate Decodable / Encodable support?
### Problem
With the current implementation, everything relies on `T: Codable`.
So for exampl…
-
# 推荐收录
## 链接
https://github.com/GodL/Animatable
## 理由
使用swift PropertyWrapper调用动画的一种方式
## 推荐人信息
如果收录这个资源,我们会在点评后面说明推荐信息人。
-
Hello 👋
First of all, thank you for making this! I'm creating a new API and I wanted to make sure I had doc from the start. This is so great 😊
I'm having troubles getting my Fluent model to pr…
-
What if `store(in:)` were called from multiple threads? Wouldn't that break the current implementation?