🚨 The automated release from the master branch failed. 🚨

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

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 fix 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 are 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 for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization 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 is a Feature Proposal

Description

Store implements subscribe and subscribeOnce methods. The callbacks are fired in the component's scope only. Allow the store to fire its subscribers in the given context like:

StoreFacade().subscribe("start", m._onStart, m)

' in the store's _notify function:
functionCall(listener.callback[0], [value], m)

This is a Bug Report

Description

• What went wrong?
  When a user navigates back, m.top.previousRoute in Router.brs is updated with a copy of a current activatedRoute
  https://github.com/getndazn/kopytko-framework/blob/master/src/components/router/Router.brs#L25

• What did you expect should have happened?
  I would expect that m.top.previousRoute points to the previous route in the history (the one that would be open when another back journey happens)

If an ID or no ID specified is not specified for each node element, at some point the app will crash.

• Build process should auto assign a unique ID to a node element if not specified.
• If there is an ID check against all others to make sure it differs.

Some teams were automatically added in order to give access to all the engineers to your repository.

If you have any queries, please contact [email protected].

🤖 Link to my robotic code

HttpResponse rawData could be any proper JSON type

Description

The current interface of HttpResponse sets rawData type to assocArray, however, rawData could be also an array.

So when it is an array the rawData is not set at all.

This is a Feature Proposal

Description

HttpResponseCreator._parseUrlEventContent function returns {} when ParseJSON is invalid. It may lead to caching invalid responses. At this point, the app knows that the response body is a non-empty string and JSON format is expected. Thus failed JSON parsing suggests that body is corrupted, and caching it may lead to unexpected behavior.

prototype._parseUrlEventContent = function (urlEvent as Object) as Object
  if (NOT m._isJsonResponse(urlEvent)) then return {}

  content = urlEvent.getString()
  if (content = "") then return {}

  data = ParseJSON(content)
  if (data = Invalid) then return {}

  return data
end function

This is a Feature Proposal

Description

What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.

HTTP responses' headers often contain useful info, eg: response caching rules. I propose that HttpResponse exposes the response headers.

If there is additional config how would it look?

N/A

Similar or dependent issues:

N/A

Some teams were automatically added in order to give access to all the engineers to your repository.

If you have any queries, please contact [email protected].

🤖 Link to my robotic code

Hi,

Is there a way to do a full reset of the app? not just destroyKoptko(). As I am loading the app from 0?

Thanks!

Curious if you had any thoughts on brighterscript integration at all in the future or if so, would you be interested in myself helping to make it happen?

I've gotten really used to the nice syntax of brighterscript and it makes things feel very clean and integrated so wasn't sure if you had considered it at all?

This is a Feature Proposal

A separate documentation page for the integration scenario would be helpful so devs using Kopytko (renderer) may easily find a solution for this case.

Description

Currently in the renderer.md there is a description of how to integrate with Kopytko e.g. in the RowList's tile component.

The entire section Using Kopytko components in the non-Kopytko environment could be extracted and described more widely with some usage examples either for the itemComponent for the RowList and for other cases as well (e.g. Kopytko root managed from an existing component in the app that cannot be modified)