deanrad / antares-ts Goto Github PK

• Create, export after rxjs utility
• Re-create the first program i ever made - the scrolling blip from Kitt on Knight Rider
• And port it to my first canvas app with very little pain!
• best ones: File writing has enough steps in it actually!

Working on demos, I've realized that people need to feel ergonomically what its like to do stuff with Antares (much like DHH did in his demo).

Introduce "muted" concurrency mode where future renders are silently not run while another render is in progress.... Justification: command is running in terminal, you type and hit Enter, should that take effect? Or should it be silently dropped since you didn't know the output of the previous command

• Show DevTools
• Dispatches to store as filter.

Snapshots

As a by-product of complex async behavior, let me assert on whole tons of conditions without arduously specifying in the language of test assertions.

Scripted, or interactive - toggle at will

Since an Observable of input is the abstraction that drives the test processing and assertions, it's easy-peasy to swap out a user-driven one for a scripted one. #winning

A blog post can focus on a trivial problem like this, but a demo should use something closer to real life.

With blessed https://github.com/chjj/blessed

Will require addition of { context } to an ActionStreamItem and a 2nd argument to agent.process to become that context.

• Pass as the actual JS context object to a renderer as well?

@rematch/core has an example like this to check out

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

This requires being able to mix in agent properties in at construction time, and having a filter that can mix those properties in to the meta of an action.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

A game should be created which demos Antares triggers, and renderers:

• Console based game
• Displays one of 10 fruit upon that key being pressed
• Fruit: [🍋🍊🍍🍏🍓🥝🌽🥕🥑🍌]
• Gets extended to print say 9 bananas, or 2 tangerines
• While running asynchronously - overlap
• SwitchMap can show the difference
• Trigger stream can be originated from console, or hardcoded.

The problem was NPM had expired all tokens.

This new one (62b77770-02d7-4d48-bb9f-54398009b5aa) was created and set for Travis CI, and a new build published.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

• CSS: https://wingkwong.github.io/react-quiz-component/
• Storybook: https://www.learnstorybook.com/react/en/composite-component/
• UI
• Use rematch for multiple model example: https://runkit.com/deanius/test-setlist-endpoint

https://github.com/kimobrian/GraphQL-Express
https://github.com/kimobrian/GraphQL-React-Apollo

• Note effect on bundle-size - No larger!
• Publish new version (2.1.1?)
• Update demos
• Documentation looks OK

Renderers to create an ever-more elaborate chain of logic

• Set up reducer for game state
• Kick out invalid moves
• Add piece-taking rules and exceptions
• Add enumerating of allowed moves
• Add additional allowed moves (castling)
• Add additional game state
• Add additional allowed moves (en-passant)

• RabbitMQ-style routingKeys: '#' - any segments - * one segment eg 'Users.*'
• Is notifying the parent a sync or async event?
• If building on socket.io, utilize the server-side ack
  #multi-agent

action: agent/p/subscribe

Flesh out with tests what it means for 2 agents (in one process) to publish/subscribe observables

Bottom line is that batching-type transforms (bufferCount, etc) will not yield asi's into renderers, but rather batchesof ASIs.. Either way that kinda makes it unclear how to track completed for a given action. So we silently don't. For now.

def8e99 introduces short-circuits

Made static images for modes serial, parallel, cutoff

So - the Fruit Game - if driven by a deterministic observable - its output on multiple platforms could be compared, creating a sort of 'hash' of all its behavior in the event of:

• sync/async renderers
• renderers that die
• mergeMap/switchMap

This can ensure that any platform specific changes can be picked up on / guaranteed.

https://www.npmjs.com/package/badge-size
https://github.com/badges/shields

With blessed https://github.com/chjj/blessed?