Conversation
|
🤖 Here's your preview: https://pv4ef-vqaaa-aaaak-qidga-cai.icp0.io/docs |
|
This seems a great start, Luc! I assume we want something similar for cycles cost, although, as @mraszyk pointed out in the interface spec meeting, it should probably be a separate call since it's going to return Are we planning to move implementation forward on the replica side soon? Is that driven by the execution team @dsarlis? |
This would be a discussion point. I cannot promise soon but we can discuss potential timelines. |
About this point, yeah, the cycles cost would technically need to return The decision would be part of the ticket that we have filed on our side and @michael-weigelt will most likely take on at some point. I personally have a slight preference for the higher level approach of having apis return directly the costs (we can then do some more clever stuff on the replica that is harder to perform on the user level, whether it's CDK or canister code) and it seems more user friendly. But we would have to see what makes the most sense at an API level (the downside of direct costs, is that they depend on size of requests in many cases, making it harder to see a unified API for all costs -- as opposed to a simpler "give me this fee and that fee"). |
|
Superseded by dfinity/portal#3754 |
Add function to query current resource limit for the canister.