v2.0 Tracking Issue
See original GitHub issueAs mentioned in #262 request
is deprecated. If we are replacing it with something else it’s a breaking change and needs to be done as a major release, thus tracking towards v2.0.
An incomplete list of things to be done before v2.0
- Replace deprecated
request
dependency,axios
may be the best contender.fetch
may not work as intended for the test suite but would otherwise be the clear winner. - Remove deprecated endpoints
- Look into what to do with Proxies and TypeScript #221
- Remove underscore function calls maps
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Tracking issue for 2.0.0 · Issue #388 · lestrrat-go/jwx - GitHub
The items in this issue are currently either low-priority, or require enough changes that it would have significant impact on the users.
Read more >Hand Tracking v2.0 Still Not Applied - Oculus Forum
Hello,. So around a good few months back Hand Tracking v2.0 was released, improving tracking and estimation of where hands are when not...
Read more >Issue Tracking 2.0 - elmah.io Blog
Learn about the built-in issue tracker on elmah.io. Assign errors to a developer to make sure that all of the bugs in your...
Read more >postgresql - EF Core 2.0 update - tracking issue - Stack Overflow
Okay! got the problem in your code. You didn't map the updated entity to the existing entity that you pulled from the database....
Read more >Issues 2.0: The Next Generation | The GitHub Blog
Issues 2.0 : The Next Generation. Issue management: the final frontier. Almost two years ago to the day, GitHub launched an issue tracker....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think a neat solution might be that proxies are simply of type Partial<SnoowrapObject>, and fetch returns a full SnoowrapObject. This would allow for more type safety as it would become obvious at compile time whether a variable is being accessed before it is assigned.
@OmgImAlexis Yeah I didn’t think about it at the beginning. I realized that we can just let developers install polyfills separately instead of including them on the library.
Anyway, I already made a progress with
axios
, I even added support for some old properties from therequest
API to gain a maximum backward compatibility.