Stream Key Button #7127
|
@ -22,6 +22,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
|
|||
- Clicking on the title of a floating player will take you back to the list ([#6921](https://github.com/lbryio/lbry-desktop/pull/6921))
|
||||
- Fix floating player stopping on markdown or image files ([#7073](https://github.com/lbryio/lbry-desktop/pull/7073))
|
||||
- Fix list thumbnail upload ([#7074](https://github.com/lbryio/lbry-desktop/pull/7074))
|
||||
- Stream Key is now hidden. ([#7127](https://github.com/lbryio/lbry-desktop/pull/7127))
|
||||
|
||||
## [0.51.2] - [2021-08-20]
|
||||
|
||||
|
@ -1955,4 +1956,4 @@ This release includes a breaking change that will reset many of your settings. T
|
|||
|
||||
- Use local file for publishing
|
||||
- Use local file and html5 for video playback
|
||||
- Misc changes needed to make UI compatible with electron.
|
||||
- Misc changes needed to make UI compatible with electron.
|
7
ui/component/copyableStreamkey/index.js
Normal file
|
@ -0,0 +1,7 @@
|
|||
![]() Renamed Renamed
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
||||
import { connect } from 'react-redux';
|
||||
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
||||
import { doToast } from 'redux/actions/notifications';
|
||||
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
||||
import CopyableStreamkey from './view';
|
||||
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
||||
|
||||
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
||||
export default connect(null, {
|
||||
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
||||
doToast,
|
||||
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
||||
})(CopyableStreamkey);
|
||||
![]() Rename to Rename to `CopyableStreamkey`
![]() Renamed Renamed
|
93
ui/component/copyableStreamkey/view.jsx
Normal file
|
@ -0,0 +1,93 @@
|
|||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
// @flow
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
import * as ICONS from 'constants/icons';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
import { FormField } from 'component/common/form';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
import Button from 'component/button';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
import React, { useRef, Fragment } from 'react';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
type Props = {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
copyable: string,
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
snackMessage: ?string,
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
doToast: ({ message: string }) => void,
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
primaryButton?: boolean,
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
name?: string,
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
onCopy?: (string) => string,
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
enableMask?: boolean,
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
};
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
export default function CopyableStreamkey(props: Props) {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
const { copyable, doToast, snackMessage, primaryButton = false, name, onCopy, enableMask = true } = props;
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
const input = useRef();
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
function copyToClipboard() {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
const topRef = input.current;
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
if (topRef[1].type === 'password') {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
navigator.clipboard.writeText(topRef[1].defaultValue);
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
if (topRef[1].type === 'text') {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
topRef[1].select();
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
if (onCopy) {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
onCopy(topRef[1]);
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
document.execCommand('copy');
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
function checkMaskType() {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
if (enableMask === true) {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
return 'password';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
if (enableMask === false) {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
return 'text';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
function showStreamkeyFunc() {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
const topRef = input.current;
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
if (topRef[1].type === 'password') {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
topRef[1].type = 'text';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
topRef[0].innerText = 'Hide';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
return;
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
if (topRef[1].type === 'text') {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
topRef[1].type = 'password';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
topRef[0].innerText = 'Show';
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
return (
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
<Fragment>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
<form ref={input}>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
<div>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
<label name="livestream-key">Stream key</label>{' '}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
<Button
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
className="button--link"
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
label={__('Show')}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
onClick={() => {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
showStreamkeyFunc();
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
/>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
</div>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
<FormField
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
type={checkMaskType()}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
className="form-field--copyable-streamkey"
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
readOnly
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
name={name}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
value={copyable || ''}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
inputButton={
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
<Button
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
button={primaryButton ? 'primary' : 'secondary'}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
icon={ICONS.COPY}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
onClick={() => {
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
copyToClipboard();
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
doToast({
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
message: snackMessage || __('Text copied'),
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
});
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
/>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
/>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
</form>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
</Fragment>
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
);
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
||||
}
|
||||
![]() Rename to actual function name for clarity Rename to actual function name for clarity
![]() Issues:
Take a look at how to use A rough guide:
Issues:
- The "Show" button didn't work for me.
- This is still not the React-way -- normally, we don't directly tweak the DOM.
- The use of `<form>` is weird, as we are not submitting anything.
Take a look at how to use `useState`.
A rough guide:
- We probably don't need `<form>` and `type=password`
- Without `password`, you don't have to change the way you perform the copy anymore.
- Create a state, e.g. `showKey`
- Replace `copyable` with asterix if state is hidden
- e.g. `value={showKey ? copyable || '' : '***')`
- Can make the asterix the same length if you want.
![]() Button is fixed. Button is fixed.
I'm not using Dom, I'm using what was already in the file itself.
The `<form>` is being used to hold the main reference instead of a single FormField item.
![]()
MergingIt works, and the changes are localized in 1 component, so good to go for now. Thanks! - The ref was originally used to highlight the text (i.e. `.select()`) when being copied, which we couldn't do via React.
- By default, we don't alter text directly that way. Use states.
- `<form>` is not the right tag for that use-case. A `<div>` would probably do.
## Merging
It works, and the changes are localized in 1 component, so good to go for now. Thanks!
|
|
@ -13,6 +13,7 @@ import { Lbry } from 'lbry-redux';
|
|||
import { toHex } from 'util/hex';
|
||||
import { FormField } from 'component/common/form';
|
||||
import CopyableText from 'component/copyableText';
|
||||
import CopyableStreamkey from 'component/copyableStreamkey';
|
||||
import Card from 'component/common/card';
|
||||
import ClaimList from 'component/claimList';
|
||||
import usePersistedState from 'effects/use-persisted-state';
|
||||
|
@ -186,7 +187,7 @@ export default function LivestreamSetupPage(props: Props) {
|
|||
copyable={LIVESTREAM_RTMP_URL}
|
||||
snackMessage={__('Copied')}
|
||||
/>
|
||||
<CopyableText
|
||||
<CopyableStreamkey
|
||||
primaryButton
|
||||
name="livestream-key"
|
||||
label={__('Stream key')}
|
||||
|
|
Rename to
CopyableStreamkey