question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Include unsupported fields in separate CEconItem property

See original GitHub issue

Per #224 and #194, non game-agnostic properties should not be included in CEconItem, which makes complete sense. However, it might be beneficial to add something like an auxiliary property which contains everything included in the inventory response that doesn’t fit an existing property. This way, non game-agnostic properties can be included in a game-agnostic way, and used when desired without cluttering the normal CEconItem.

For example, CS:GO adds a cache_expiration property to items in trade lock, so that would be included in CEconItem like so:

CEconItem {
    market_hash_name: "P250 | Sand Dune (Minimal Wear)",
    ...
    auxiliary: {
        cache_expiration: "2019-09-28T07:00:00Z"
    }
}

In essence, this makes it so that users who require game-specific properties can access them easily without cluttering CEconItem with game-specific logic or variables.

I’d be more than happy to implement this if desired.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
DoctorMcKaycommented, Sep 21, 2019

If you’re talking about the cache_expiration property available on Steam item objects, that’s not a CS:GO-specific property. It’s a generic Steam property that all games can use. Steam coupons use it for when they expire, for example.

As for your proposal, I think I would rather leave it up to external modules to do stuff like this. For example, you could create a package steam-csgo-item-parser or something that you pass a CEconItem object to and it could return what you’re interested in.

Read more comments on GitHub >

github_iconTop Results From Across the Web

[Enhancement] Add a method to see when CEconitem will be ...
CEconItem is a game-agnostic interface, so unfortunately trade lock ... Include unsupported fields in separate CEconItem property #229.
Read more >
Unsupported fields cannot be used for authoring—ArcGIS Pro
Right-click the layer in the Contents pane and click Properties. Click Display and choose a field for Display field other than the area...
Read more >
Error: 00241 Field <field_name> cannot be used for symbology
The error message is returned and publishing of the feature layer fails in ArcGIS Pro. Cause. An unsupported area or length field is...
Read more >
AppSourceCop Error AS0036 - Business Central
Modifying table field properties can lead to destructive changes that will break the upgrade of ... Unsupported table field property change ...
Read more >
Hidden fields and unsupported fields in request types
Each request type in your Jira Service Management is based on an issue type. Every issue typed has a set of allowed and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found