Prepare for 1.0 release
See original GitHub issue- allow beta branch to simmer a bit longer
- #284
Post 1.1
- replace more pretender mocks with Mirage (essentially the same thing…just a bit more re-useable)
- Put together an example with a Phoenix / Elixir backend + pagination (as an example)
- deprecate the following in
1.1
- boundParameters, updateInfinityModel, _notifyInfinityModelUpdated
Let me know if anybody has anybody has issues or questions about removing the above deprecated methods for the 1.0 release! 📦
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
5 Things To Do Before Grounded 1.0 - Full Release - YouTube
In this video I discuss things that I think we should be working on before the full release of Grounded 1.0. Hope You...
Read more >OsmSharp/io-api - Prepare for 1.0 release by HarelM - GitHub
In theory, merging this to main would result in a creation of package. If this will work there's no other work to be...
Read more >[NETC-33] Prepare for 1.0 Release - Jira
This task is a parent placeholder for subtasks that need to be completed prior to 1.0 release. Environment. None. Subtasks. 100% Done. Issue...
Read more >Bytecode Alliance Preparing For Wasmtime 1.0 Releasing ...
The Bytecode Alliance is preparing to formally release Wasmtime 1.0 on 20 September. Prior to that v1.0 milestone there has been a push...
Read more >[#TEXT-53] Prepare site for 1.0 release - ASF JIRA - Apache
Prepare site for 1.0 release. Status: Assignee: Priority: ... Description. Make sure that all aspects of the site are prepared for release.
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
@thomassnielsen Hey! 👋 The main API addition is #287 and that will hopefully go in this week. The remaining items will go into future minor releases (edited the desc).
I’ve been using that PR in a project and no bugs so far, so feeling confident on the new (and improved API). I think just needs one more review and possibly an approval from @hhff!
1.0 released! Check it out! Will close and open another issue with some nice to haves post 1.0.