What I Want
I want to fixed side menu it should not scrolling with my data.

Description
I have installed react-admin in my react web App project but i am facing side menu scrolling issue. Side menu is scrolling with data.

Steps to reproduce:
I have following the same example that is providing by react-admin and in this example issue can be reproduce on dashboard.
If we will

Bug Report

Steps

1. Go to documentation for Ribbon type labels
2. Click the CodeSandbox link in the top-right corner of the examples segment
3. When the checkmark appears, click it to be taken to CodeSandbox
4. When CodeSandbox loads, notice that the URLs for the tags have doubled the URL prefix so they are: `<Im

The list looks outdated in today's context so if anyone looking for repositories to contribute for hacktoberfest. Then this might be a good place.

Our main tasks would be

• Add new content which you find useful for yourself while making sure that it isn't already there
• If you think any of the content is already there but is now deprecated then you can help in refactoring that as well. **Pl

I'm having trouble groking how to get data out of the fetch::Request::fetch() method.

Sorry this is more of a support request than an issue.

Calling phonon.navigator().changePage(pageName) does not do anything if pageName is a prefix of phonon.navigator().currentPage.

The following conditions prevents unnecessary changes from the current page to the current page, but it prevents changes to other pages with the current page name as a prefix, too.

if(window.location.hash.indexOf(hash) === -1 && opts.useHash) {
   window.locat

make build-cli

GO111MODULE=on
GOOS=darwin GOARCH=amd64 go build -o oak cmd/oak-cli/main.go

github.com/spf13/cobra

../../spf13/cobra/command.go:31:25: undefined: pflag.ParseErrorsWhitelist
Makefile:6: recipe for target 'build-cli' failed
make: *** [build-cli] Error 2

To be backwards compatible the TKO library needs to be polyfilled. Examples of ES6 features that need polyfill:

• Generators
• Object.entries/Object.assign
• Backticks
• => functions
• Spreads

Here are some things needed to polyfill:

• WeakMap (?)
• Object.assign / entries
• Promise
• Generators
• Map + Set
• Node.remove
• Symbol, Symbol.interator / observable
• String::star

Add to documentation to particular component information about it's inheritance tree (e.g. WebItem->Rectangle->Item), so inherited properties and methods can be easily accessible.
Having kind of inheritance structure would be nice:
"interits": {
"name": "Rectangle",
"ref": "core/Ractangle",
"inherits": {
"name": "Item",
"ref": "core/Item",
"inherits

Feature Request

Description

Add an isOpen prop to toggle-section-header so that it can be programmatically opened and closed.

Additional Context / Screenshots

@ Mentions

@mjhenkes recommended opening an issue.

See yewstack/yew#233 (comment) for context.

Essentially, the desired behavior is: if an edit for a field (e.g. an input or text area) is 'rejected' (i.e. not applied to the model), the render should not update. In react this is known as 'controlled components'.

In squark you can test this by applying the patch I've pasted at the bottom and then editing the 'new item' input element on the

In the utils server we are using too many custom functions for the magazines fake data. We could replace that using the fake-data-generator as a dev-dependency.

Current models: please respect the current type of each property

magazine: {
  id: Number, // faker random number
  name: String, // faker random words
  articles: 

Currently, the only documentation of the project is the Middleman's index page, where we can see a list of all the pages styled, and the toolkit. The toolkit contains an example of each one of the components used to create the different pages.

We need to define:

• What kind of documentation does the project need? (toolkit, page examples, how to install, style guidelines, etc.).
• What do we

[WIP] Working in progress

This feature allows older components to co-exist with newer ones, and selective live-on-air updates managed by the application itself.

Also, completely solves the problem of browser cache when publishing updates to the app in one or more components. The versioning strategy saves each component's version in an unique filename, which provides an unique URL.