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.
Suggestions for expanding the API
See original GitHub issueNot sure if we’re supposed to be able to use this function, but the docs for the Space API don’t indicate that you can inspect the unit on a given space by calling space.getUnit(). Is there a reason that was left out, or was that just an oversight?
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (12 by maintainers)
Top Results From Across the Web
7 ideas for the future of APIs | Google Cloud Blog
1. API security takes center stage. · 2. Microservices APIs are gaining speed. · 3. Event-driven architecture (EDA) continues its big comeback. ·...
Read more >8 Tips for Optimizing an API - DreamFactory Software- Blog
Want to know how optimizing an API will enable better performance? These tips will have you on your way to getting the most...
Read more >3 Ways to Make Your API Responses Flexible - Zapier
3 Ways to Make Your API Responses Flexible · Include/Exclude Certain Fields · Expand Certain Fields · Go All In With GraphQL ·...
Read more >Forrester: How to expand your API strategy | Computer Weekly
Application programming interfaces (APIs) expand ecosystems and market ... Refine the ideas and only then allow value analysis to sift ...
Read more >Linking and Resource Expansion: REST API Tips - Stormpath
Learn the many ways to add linking and resource expansion to your REST JSON API, and the particularly elegant approach taken by Stormpath....
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 Free
Top 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
Initially, I was thinking on adding a sense
warrior.wounds(). This would return an array of the wounds gotten by the warrior in the last turn. Each wound would have a direction (forward, right, backward, or left) and a damage amount. That would allow the player to identify where the greatest damage is coming from and subsequently, where the greatest threat is located. Thoughts?@mattdiamond I just released v0.3.0, which reorganizes the Player API a bit. This should align the codebase better with some additions that could come in the future, like
.isMelee()and.isRanged()for the Unit API.