Swift codeable for date keys
up vote
1
down vote
favorite
I'm trying to do a codeable struct for a Financial API that returns
"Time Series (Daily)": {
"2018-11-16": {
"1. open": "190.5000",
"2. high": "194.9695",
"3. low": "189.4600",
"4. close": "193.5300",
"5. volume": "36928253"
},
"2018-11-15": {
"1. open": "188.3900",
"2. high": "191.9700",
"3. low": "186.9000",
"4. close": "191.4100",
"5. volume": "46478801"
},
"2018-11-14": {
"1. open": "193.9000",
"2. high": "194.4800",
"3. low": "185.9300",
"4. close": "186.8000",
"5. volume": "60800957"
}
}
I can't use CodingKeys, as the keys are dates and they vary. Not sure how to tackle this.
ios json swift
add a comment |
up vote
1
down vote
favorite
I'm trying to do a codeable struct for a Financial API that returns
"Time Series (Daily)": {
"2018-11-16": {
"1. open": "190.5000",
"2. high": "194.9695",
"3. low": "189.4600",
"4. close": "193.5300",
"5. volume": "36928253"
},
"2018-11-15": {
"1. open": "188.3900",
"2. high": "191.9700",
"3. low": "186.9000",
"4. close": "191.4100",
"5. volume": "46478801"
},
"2018-11-14": {
"1. open": "193.9000",
"2. high": "194.4800",
"3. low": "185.9300",
"4. close": "186.8000",
"5. volume": "60800957"
}
}
I can't use CodingKeys, as the keys are dates and they vary. Not sure how to tackle this.
ios json swift
here's a better link to the JSON alphavantage.co/…
– Fat Mike
Nov 22 at 0:29
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm trying to do a codeable struct for a Financial API that returns
"Time Series (Daily)": {
"2018-11-16": {
"1. open": "190.5000",
"2. high": "194.9695",
"3. low": "189.4600",
"4. close": "193.5300",
"5. volume": "36928253"
},
"2018-11-15": {
"1. open": "188.3900",
"2. high": "191.9700",
"3. low": "186.9000",
"4. close": "191.4100",
"5. volume": "46478801"
},
"2018-11-14": {
"1. open": "193.9000",
"2. high": "194.4800",
"3. low": "185.9300",
"4. close": "186.8000",
"5. volume": "60800957"
}
}
I can't use CodingKeys, as the keys are dates and they vary. Not sure how to tackle this.
ios json swift
I'm trying to do a codeable struct for a Financial API that returns
"Time Series (Daily)": {
"2018-11-16": {
"1. open": "190.5000",
"2. high": "194.9695",
"3. low": "189.4600",
"4. close": "193.5300",
"5. volume": "36928253"
},
"2018-11-15": {
"1. open": "188.3900",
"2. high": "191.9700",
"3. low": "186.9000",
"4. close": "191.4100",
"5. volume": "46478801"
},
"2018-11-14": {
"1. open": "193.9000",
"2. high": "194.4800",
"3. low": "185.9300",
"4. close": "186.8000",
"5. volume": "60800957"
}
}
I can't use CodingKeys, as the keys are dates and they vary. Not sure how to tackle this.
ios json swift
ios json swift
edited Nov 22 at 0:33
Paulw11
66.2k108098
66.2k108098
asked Nov 22 at 0:27
Fat Mike
112
112
here's a better link to the JSON alphavantage.co/…
– Fat Mike
Nov 22 at 0:29
add a comment |
here's a better link to the JSON alphavantage.co/…
– Fat Mike
Nov 22 at 0:29
here's a better link to the JSON alphavantage.co/…
– Fat Mike
Nov 22 at 0:29
here's a better link to the JSON alphavantage.co/…
– Fat Mike
Nov 22 at 0:29
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
You can try
struct Root: Codable {
let timeSeriesDaily: [String: TimeSeriesDaily] // make key as String to generalize all keys
enum CodingKeys: String, CodingKey {
case timeSeriesDaily = "Time Series (Daily)"
}
}
struct TimeSeriesDaily: Codable {
let the1Open, the2High, the3Low, the4Close,the5Volume: String
enum CodingKeys: String, CodingKey {
case the1Open = "1. open"
case the2High = "2. high"
case the3Low = "3. low"
case the4Close = "4. close"
case the5Volume = "5. volume"
}
}
May you forgot the date as key, that's problem
– Quoc Nguyen
Nov 22 at 0:50
1
@QuocNguyen the date-model are =>let timeSeriesDaily: [String: TimeSeriesDail
to overcome vary of keys as if hardcoded the decoding will fail so we make it a dictionary
– Sh_Khan
Nov 22 at 0:53
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
You can try
struct Root: Codable {
let timeSeriesDaily: [String: TimeSeriesDaily] // make key as String to generalize all keys
enum CodingKeys: String, CodingKey {
case timeSeriesDaily = "Time Series (Daily)"
}
}
struct TimeSeriesDaily: Codable {
let the1Open, the2High, the3Low, the4Close,the5Volume: String
enum CodingKeys: String, CodingKey {
case the1Open = "1. open"
case the2High = "2. high"
case the3Low = "3. low"
case the4Close = "4. close"
case the5Volume = "5. volume"
}
}
May you forgot the date as key, that's problem
– Quoc Nguyen
Nov 22 at 0:50
1
@QuocNguyen the date-model are =>let timeSeriesDaily: [String: TimeSeriesDail
to overcome vary of keys as if hardcoded the decoding will fail so we make it a dictionary
– Sh_Khan
Nov 22 at 0:53
add a comment |
up vote
1
down vote
You can try
struct Root: Codable {
let timeSeriesDaily: [String: TimeSeriesDaily] // make key as String to generalize all keys
enum CodingKeys: String, CodingKey {
case timeSeriesDaily = "Time Series (Daily)"
}
}
struct TimeSeriesDaily: Codable {
let the1Open, the2High, the3Low, the4Close,the5Volume: String
enum CodingKeys: String, CodingKey {
case the1Open = "1. open"
case the2High = "2. high"
case the3Low = "3. low"
case the4Close = "4. close"
case the5Volume = "5. volume"
}
}
May you forgot the date as key, that's problem
– Quoc Nguyen
Nov 22 at 0:50
1
@QuocNguyen the date-model are =>let timeSeriesDaily: [String: TimeSeriesDail
to overcome vary of keys as if hardcoded the decoding will fail so we make it a dictionary
– Sh_Khan
Nov 22 at 0:53
add a comment |
up vote
1
down vote
up vote
1
down vote
You can try
struct Root: Codable {
let timeSeriesDaily: [String: TimeSeriesDaily] // make key as String to generalize all keys
enum CodingKeys: String, CodingKey {
case timeSeriesDaily = "Time Series (Daily)"
}
}
struct TimeSeriesDaily: Codable {
let the1Open, the2High, the3Low, the4Close,the5Volume: String
enum CodingKeys: String, CodingKey {
case the1Open = "1. open"
case the2High = "2. high"
case the3Low = "3. low"
case the4Close = "4. close"
case the5Volume = "5. volume"
}
}
You can try
struct Root: Codable {
let timeSeriesDaily: [String: TimeSeriesDaily] // make key as String to generalize all keys
enum CodingKeys: String, CodingKey {
case timeSeriesDaily = "Time Series (Daily)"
}
}
struct TimeSeriesDaily: Codable {
let the1Open, the2High, the3Low, the4Close,the5Volume: String
enum CodingKeys: String, CodingKey {
case the1Open = "1. open"
case the2High = "2. high"
case the3Low = "3. low"
case the4Close = "4. close"
case the5Volume = "5. volume"
}
}
answered Nov 22 at 0:31
Sh_Khan
36.2k51125
36.2k51125
May you forgot the date as key, that's problem
– Quoc Nguyen
Nov 22 at 0:50
1
@QuocNguyen the date-model are =>let timeSeriesDaily: [String: TimeSeriesDail
to overcome vary of keys as if hardcoded the decoding will fail so we make it a dictionary
– Sh_Khan
Nov 22 at 0:53
add a comment |
May you forgot the date as key, that's problem
– Quoc Nguyen
Nov 22 at 0:50
1
@QuocNguyen the date-model are =>let timeSeriesDaily: [String: TimeSeriesDail
to overcome vary of keys as if hardcoded the decoding will fail so we make it a dictionary
– Sh_Khan
Nov 22 at 0:53
May you forgot the date as key, that's problem
– Quoc Nguyen
Nov 22 at 0:50
May you forgot the date as key, that's problem
– Quoc Nguyen
Nov 22 at 0:50
1
1
@QuocNguyen the date-model are =>
let timeSeriesDaily: [String: TimeSeriesDail
to overcome vary of keys as if hardcoded the decoding will fail so we make it a dictionary– Sh_Khan
Nov 22 at 0:53
@QuocNguyen the date-model are =>
let timeSeriesDaily: [String: TimeSeriesDail
to overcome vary of keys as if hardcoded the decoding will fail so we make it a dictionary– Sh_Khan
Nov 22 at 0:53
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422300%2fswift-codeable-for-date-keys%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
here's a better link to the JSON alphavantage.co/…
– Fat Mike
Nov 22 at 0:29