tomasz-zdeb / daml-sandbox

Step by step beginner guide on how to use Daml smart contract programming language and framework

Tomasz Zdeb 👨🏻‍💻

🏢 Software Engineer | 👨🏻‍🎓 Computer Science Graduate

😃 Social: I enjoy being around others and engaging in social activities.
💪 Resilient: I am open to learning from criticism, even if it's not pleasant.
🧠 Logical and intuitive: I tend to use a combination of logic and intuition when solving problems.
⚖️ Balanced risk-taker: I generally prefer playing it safe but am willing to take risks occasionally.
🗂️ Organized: I am highly organized and likely appreciate structure in your life.
🔧🎨 Versatile: I possess both creative and practical skills, allowing me to adapt to various situations.
🚀 Leadership: I am comfortable taking charge and leading others in group settings.
🏃‍♂️ Stress avoidance: I may sometimes struggle with stress and tend to avoid it.
📅 Routine-oriented: I prefer routine but find a lot of joy in spontaneous activities.
💞 Considerate: I prioritize others' needs but also take care of myself.
🔮 Future-focused: I tend to plan for and think about the future.
🤐 Reserved: I find it difficult to express my emotions to others.
🕵️ Analytical: I approach situations with a more analytical mindset.
🌟 Open to novelty: I enjoy trying new things and exploring new experiences.
🤲 Altruistic: I am motivated by helping others succeed.
🗣️ Verbal communicator: I prefer expressing yourself through speaking rather than writing.
⏳ Work-life balance awareness: I recognize the importance of work-life balance but struggle to maintain it consistently.
💡 Decision-making: I use a combination of analysis and gut feeling when making decisions.
🌟 Confident: I have a relatively high level of self-confidence.
🌏 Holistic thinker: I tend to focus on the big picture before diving into the details.

daml-sandbox's Issues

Finish the choices section

To finish the explanation of templates - the most important concept in Daml environment, finishing choices section in the guide should take place, to provide necessary information on the topic.

JSON API returns empty array on http://localhost:7575/v1/query GET with 200 response

While GET request is executed on http://localhost:7575/v1/query endpoint with JWT authorization, empty array is returned as a response.

I would like to:

• define what causes the response to be an empty array
• make the response contain contract data

I used Curl and Postman to try the request, both with the same result.

Headers

• Authorization Bearer <JWT-token>
• Default postman headers

JWT is generated as stated in Official Documentation.

Response

{
    "result": [],
    "status": 200
}

If JWT is not present: 401 Authentication Error code is thrown

Warning on non-issuer to non-issuer token offer

In Main.daml in manual testing script, when trying to offer a token from current owner which is not an issuer to another party (also not issuer) following warning message appears:

Tried to fetch or exercise -homePackageId-:Token:Token on contract 001f8b1d815e42f839d23a224e5e352f2b3cfe32b5d866c72a7d232b545c865e27 but none of the reading parties [Bob] are contract stakeholders [Alice,UserAdmin]. Use of divulged contracts is deprecated and incompatible with pruning. To remedy, add one of the readers [Bob] as an observer to the contract.

Though contracts behave as expected.

It would be nice to:

• figure out why the warning appears
• eliminate the cause.