-
## Description
Parity feature
When embedding another BOS component, it should be possible to provide a blockheight at which a version of that component was published in order to lock to that versi…
-
## Is your feature request related to a problem? Please describe.
There are two problems at the moment:
1. In order to post a new idea/solution/reply on DevHub or like a post on DevHub users are…
frol updated
9 months ago
-
**Describe the bug**
All of the links on DevHub such as in the navigation bar are redirecting to about:blank rather than the correct route.
This is related to #894
**NOTICE:** This only occurs…
-
**Is your feature request related to a problem? Please describe.**
For https://github.com/NearSocial/VM/pull/156 to work, and in order to solve #137 there cannot be any deposit or a gas amount that w…
-
**Is your feature request related to a problem? Please describe.**
When user starting to interact with gateway, they see transaction confirmation windows which are extremely confusing to the new user…
-
**Describe the bug**
All of the links on DevHub such as in the navigation bar are redirecting to about:blank rather than the correct route.
**NOTICE:** This only occurs on near.org and is not an…
-
### Description
Developers should be able to save (e.g. 'star') components that they find useful for later reference. Additionally, components should track and display how often they have been starre…
-
I have the following components:
```diff
const getRandomInt = (max) => {
return Math.floor(Math.random() * max);
}
const getPrompt = (page, cb) => asyncFetch(`https://alpha.tryhologram.art/ap…
-
Execution errors appear randomly in place of components when running near.org locally. One example is the "current component" in the "Develop" menu dropdown:
-
There are a lot of `` tags used throughout BOS that cause really inefficient page reloads or redirects due to them not being native `Next/Link` components (which use client side routing). We should fi…