text:
Bug whenever i want to start filling params, It throws an error

my config:
local lfs = require("lfs")
require('packer').startup(function(use)
    use "ray-x/lsp_signature.nvim"
    use "hrsh7th/cmp-buffer"
    use "hrsh7th/nvim-cmp"
    use "hrsh7th/cmp-nvim-lsp"
    use "https://gitlab.com/yorickpeterse/nvim-window.git"
    use "folke/trouble.nvim"
    use "williamboman/mason.nvim"
    use "neovim/nvim-lspconfig"
    use "nvim-tree/nvim-tree.lua"
    use "nvim-treesitter/nvim-treesitter"
    use "easymotion/vim-easymotion"
    use "github/copilot.vim"
    use "wbthomason/packer.nvim"
    use "preservim/tagbar" -- exuberant-ctags
end)
require("trouble").setup({
    icons = false,
    fold_open = "", --icons
    fold_closed = "",
    indent_lines = true,
    signs = {
        error = "E",
        warning = "W",
        hint = "H",
        information = "I",
        other = "O",
    },
}) --TODO refresh
require("lsp_signature").setup({
    floating_window_off_y = 0,
    floating_window_above_cur_line = true,
    fix_pos = true, -- do not auto-close floating window until I've entered all parameters
    hint_enable = false, -- do not show virtual text hint
    hint_prefix = "-> ", -- point at the current parameter, when it's present
    handler_opts = {
        border = "none",
    },
})
local cmp = require("cmp") -- TODO event listening
cmp.setup({
    mapping = {
        ["<Tab>"] = function(fallback)
            if cmp.visible() then
                cmp.select_next_item()
            else
                fallback()
            end
        end,
        ["<S-Tab>"] = function(fallback)
            if cmp.visible() then
                cmp.select_prev_item()
            else
                fallback()
            end
        end,
        ["<CR>"] = function(fallback)
            if cmp.visible() then
                cmp.confirm({
                    behavior = cmp.ConfirmBehavior.Replace, -- do not reinsert the text of the completion you've already typed when you confirm
                    select = true, -- <CR> accepts first completion
                })
            else
                fallback()
            end
        end,
        ["<C-Up>"] = function(fallback)
            if cmp.visible() then
                cmp.scroll_docs(-4)
            else
                fallback()
            end
        end,
        ["<C-Down>"] = function(fallback)
            if cmp.visible() then
                cmp.scroll_docs(4)
            else
                fallback()
            end
        end,
    },
    sources = {
        {name = "nvim_lsp"},
        {name = "buffer"},
    },
})
local lspconfig = require("lspconfig")
local servers = {"sumneko_lua", "pyright"}
for _, v in pairs(servers) do
    lspconfig[v].setup({
        capabilities = vim.tbl_extend("force", lspconfig.util.default_config.capabilities, require("cmp_nvim_lsp").default_capabilities()),
    })
end
require("mason").setup()
require("nvim-treesitter.configs").setup({
    ensure_installed = {"lua", "python"}, --parsers
    indent = {enable = true},
    --highlight = {enable = true}, --"I get query error: invalid node type at position" paragraph. Syntax highlighting
})
require("nvim-tree").setup({
    open_on_setup_file = true, -- focus on file window rather than nvim-tree
    view = {
        relativenumber = true,
        number = true,
    },
    renderer = {
        highlight_opened_files = "names",
        icons = {-- To disable the display of icons see |renderer.icons.show|
            show = {
                git = true,
                folder = false,
                file = false,
                folder_arrow = false,
            },
        },
    },
    diagnostics = {
        enable = true,
        icons = {
            hint = "H",
            info = "I",
            warning = "W",
            error = "E",
        },
    },
})
-- config centered on github copilot
local options = { -- TODO negative scrolloff
    cursorline = true,
    cursorlineopt = "screenline",
    filetype = "on", --turned on filetype detection
    foldmethod = "expr",
    foldexpr = "nvim_treesitter#foldexpr()",
    foldnestmax = 1,
    clipboard = vim.opt.clipboard + "unnamedplus" + "unnamed", --xclip required
    expandtab = true,
    hlsearch = false,
    iskeyword = vim.opt.iskeyword + "-" + "_",
    number = true,
    pumheight = 7,
    relativenumber = true,
    scrolloff = 999,
    shiftwidth = 4, -- Number of spaces to use for each step of (auto)indent
    showmode = false,
    smartindent = true, -- Do smart autoindenting when starting a new line
    softtabstop = 4, -- Number of spaces that a <Tab> counts for while performing editing operations
    tabstop = 4, -- Number of spaces that a <Tab> in the file counts for
    updatetime = 200,
}
for k, v in pairs(options) do
    vim.opt[k] = v
end
local globals = {
    tagbar_show_linenumbers = 2, -- show relative line numbers in tagbar window
    copilot_no_tab_map = true,
    tagbar_show_tag_linenumbers = 1, -- show in which line the tag is in the code
    tagbar_show_visibility = 1, -- show whether a tag is Publ, Priv or Prot
    tagbar_visibility_symbols = {
        public = "PUBL ",
        protected = "PROT ",
        private = "PRIV ",
    }
}
for k, v in pairs(globals) do
    vim.g[k] = v
end
local speed_coding = {"q", "w", "qa", "wa", "q!", "w!", "qa!", "wa!"} -- TODO define commands
-- partiallly accept GitHub copilot suggestion, word by word.
local function partiallyAccept()
    local _ = vim.fn['copilot#Accept']("")
    local suggestion = vim.fn['copilot#TextQueuedForInsertion']()
    return vim.fn.split(suggestion,  [[[ .\(\)\\\/]\zs]])[1] -- stop accepting the word/completion when we run into : dot, space, parenthesis, slash, backslash
end

local function smartIndent()
    local currLine, currCol = unpack(vim.api.nvim_win_get_cursor(0))
    --! => nore
    vim.api.nvim_command("normal! gg=G")
    vim.api.nvim_command("normal! " .. currLine .. "G")
end
-- TODO indent mode
local keymaps = { -- :h modes
    {"i", "<C-c>", 'copilot#Accept("<C-c>")', {silent = true, expr = true}},
    {"nv", "<c-w>", "<cmd>:lua require('nvim-window').pick()<CR>", {}},
    {"nv", "<leader>p", '"+p', {noremap=true}}, --xclip?
    {"nv", "<leader>y", '"+y', {noremap=true}},
    {"nv", "c", '"_c', {noremap=true}},
    {"nv", "d", '"_d', {noremap=true}},
    {"nv", "x", '"_x', {noremap=true}},
    {"i", "<c-l>", partiallyAccept, {expr=true}},
    {"n", "<c-f>", smartIndent, {}},
    {"n", "<c-d>", function()
        updateLSP(lfs.currentdir(), 1)
        vim.api.nvim_command("Trouble workspace_diagnostics")
    end, {}},
    {"nov", "F" , "<Plug>(easymotion-Fl)", {}},
    {"nov", "T" , "<Plug>(easymotion-Tl)", {}},
    {"nov", "t" , "<Plug>(easymotion-tl)", {}},
    {"nov", "f" , "<Plug>(easymotion-fl)", {}},

}

local function keymap(modes, key, value, opts)
    for i=1, string.len(modes) do
        local mode = string.sub(modes, i, i)
        vim.keymap.set(mode, key, value, opts)
    end
end

for _, v in pairs(keymaps) do
    keymap(unpack(v))
end
function updateLSP(path, depth)
    if depth == 0 then
        return
    end
    for file in lfs.dir(path) do
        local f = path..'/'..file
        if file ~= "." and file ~= ".." and lfs.attributes(f).mode ~= "directory" then
            vim.cmd("vs " .. file)
            vim.cmd("close")
        end
    end
    vim.cmd("NvimTreeRefresh")
end
local all_files = {"*.py", "*.lua"}
local autocmds = { -- TOSEE https://stackoverflow.com/questions/3837933/autowrite-when-changing-tab-in-vim
    -- TODO check if NvimTree window is alone then quit. echoDocInWin
    {{"TabNew"}, {pattern = all_files, command=":TagbarOpen"}},
    {{"TabNew"}, {pattern = "*", command=":NvimTreeOpen"}},
    {{"VimEnter"}, {pattern =  all_files, command=":NvimTreeOpen"}},
    {{"VimEnter"}, {pattern = all_files, command=":TagbarOpen"}},
    {{"CursorHoldI"}, {pattern = all_files, command=":TagbarForceUpdate"}},
}
for _, v in pairs(autocmds) do
    vim.api.nvim_create_autocmd(unpack(v))
end

Dunno if you figured this out, but this started happening for me too after installing copilot - looks like the two plugins might conflict

I am using copilot. I do not think it is related.
Might be lsp related. What LSP you are using?

Why don't you think it's related? It stops happening if the copilot plugin is disabled 😅
I'm using tsserver

@callumacrae @matteouni
Could you check if the issue still occur in latest version? Thanks!

Yeah, that seems to fix the issue for me! Amazing, I have missed this plugin :D

authors: callumacrae matteouni ray-x


text:
Errors on comment line in Russian language

When using jedi-language-server I get this error when typing or just hovering over a comment in Russian language, such thing doesn't happen with pylsp
RPC[Error] code_name = InvalidParams, message = "ValueError: `column` parameter (112) is not in a valid range (0-96) for line 5 ('# поменять на общий подход,тк из данных нужно только названи
е, uid можно хранить в MemoryStorage\\n')." data = "{'traceback': ['  File \"/Users/*****/.local/share/nvim/mason/packages/jedi-language-server/venv/lib/python3.10/site-packages/pygls
/protocol.py\", line 340, in _handle_request\\n    self._execute_request(msg_id, handler, params)\\n', '  File \"/Users/mik.dmitriev/.local/share/nvim/mason/packages/jedi-language-server/ven
v/lib/python3.10/site-packages/pygls/protocol.py\", line 264, in _execute_request\\n    self._send_response(msg_id, handler(params))\\n', '  File \"/Users/*****/.local/share/nvim/maso
n/packages/jedi-language-server/venv/lib/python3.10/site-packages/jedi_language_server/server.py\", line 267, in signature_help\\n    signatures_jedi = jedi_script.get_signatures(*jedi_lines
)\\n', '  File \"/Users/*****/.local/share/nvim/mason/packages/jedi-language-server/venv/lib/python3.10/site-packages/jedi/api/helpers.py\", line 484, in wrapper\\n    raise ValueErro
r(\\'`column` parameter (%d) is not in a valid range \\'\\n']}"

here is asciinema:
https://asciinema.org/a/586395

Looks like this problem affects not only comment but any row which contains Russian language

I think it was some bug in lsp, error doesn't occur anymore

Well, I was wrong, this bug still occurs

I end up using noice.nvim which supports signature while typing

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
[Color Casket] Unable to install

Extension – Color Casket
Author: @slavarazum
My first recently published extension unable to install from Store.

Error Message:
Failed to install extension.
Reason: Failed to decode response data
Domain: network
Time: 05:07:28.692
Service: Internal networking engine
Underlying:
	Domain: RaycastData.StoreAPIResponse.Error 1

Extension details failed to load either...

Command logo is not displayed on extension page:

Steps To Reproduce

Try to install extension from Strore
Open details

Raycast version
Version: 1.33.2

Fixed!

repo: raycast/extensions

license: MIT


text:
arguments support enum

Describe the feature and the current behavior/state.
support enum arguments
so, developer can add enum to arguments
https://developers.raycast.com/information/arguments
Will this change the current API? How?
Who will benefit from this feature?
Any Other info.

Forgot to close this but we shipped this a while ago

authors: chyroc mathieudutour


text:
Update rapidcap extension

Description

Screencast

Checklist

[ ] I read the extension guidelines
[ ] I read the documentation about publishing
[ ] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

resolves #13317

source: gharchive/pull-request


text:
Update music dislike song

Description
Dislike doesn't work now. But "love" work. I copy implementation from Love function
Screencast
It should work
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

I think that I can do not test this change because it structurally the same as for "like"

LGTM! Thank you!

@Rawnly do you know release plan for this PR?

It's not on me, let's ping @pernielsentikaer

authors: Rawnly max-mykhailenko pernielsentikaer


text:
[Things] Add the ability to copy the Things URI to the clipboard

Description
Adds the ability to copy the Things URI to the clipboard. Fixes #5232
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer @andreaselia LGTM! Thank you very much for that new feature

authors: andreaselia loris


text:
Update README.md

Fix small typo

Thanks!

authors: raycharius setchy

repo: raycharius/slack-block-builder


text:
HourLink attempt

Push to upstream shared repo

Congratulations @hourlink on sending a PR back to the original repo—did you manage to complete all the challenges without a hitch?
I see that you created 2 PRs—was there an issue towards the end?
I hope you found the course useful—if you weren't already using git for your code, hopefully this has inspired you to do so. Given that we've now launched the next series "Mastering Git", you'll be able to get started straight away!
You can now wear this #GitWarrior badge with pride—and Tweet your historic victory!

sam

authors: hourlink sammyd

repo: raywenderlich/rwTODOs

license_source: bigquery


text:
Add dialcode to empty input on mount + update cursor position on empty input focus

Hi @razagill
I added two changes to your phone input. First change adds the dialcode on mount if no value prop is passed. Also put the cursor to the end on focus after the dialcode was added to the empty input field. #greetingsfromberlin

@RRutsche Thanks a lot :)

authors: RRutsche razagill

repo: razagill/react-phone-input

license: mit


text:
Getting error after Mac OS Big Sur update

After I updated my system from Catalina to Big Sur, I am trying to install rbenv with no luck.
When I am trying following:
rbenv install 3.0.0
I am getting following error:
Downloading ruby-3.0.0.tar.gz...
-> https://cache.ruby-lang.org/pub/ruby/3.0/ruby-3.0.0.tar.gz
error: failed to download ruby-3.0.0.tar.gz
BUILD FAILED (macOS 11.1 using ruby-build 20210119)

Upon executing following command:
curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-doctor | zsh

I am getting following error:
curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

I never reproduce that.

I guess it was issue with the Mac OS Big Sur update. I was able to fix it. Thank you @hsbt

authors: hsbt subratrout

repo: rbenv/ruby-build


text:
Touch responsive

Hi,
Great Component.
I was wondering if it works for touch Events also,  for iPads or phones?
It responds to click events on desktop but doesn't responding to touch events.

@manpreetAulakh Thanks for pointing that out. v1.17.1 should work for touch devices as well. I still have to get the css look-and-feel for touch devices when dragging the card. Will do it when I have time, or if you can do that and send a PR, will be glad to merge it. Thanks!

authors: manpreetAulakh rcdexta

repo: rcdexta/react-trello


text:
Start not possible

Ran into an issue twice today where someone joined, the map ended, and then the 'start' button was greyed out. Unable to affect change by changing a new map or doing anything else. Left and created new server and it worked again.
I sent you the relevant logs in discord.

Please update your instance. I can't provide support for outdated versions of the server.

Sorry to be unclear, but I wasn't asking for support, I was informing you of an issue. I haven't upgraded since everything has been working and everyone has been on 1.29 consistently.

Issue turned out to be not related to Beatupserver.

authors: jabberjabberjabber rcelyte

repo: rcelyte/BeatUpRcelyte

license: Unlicense


text:
updated postman collection json file for blog post requests

Resolved #685.

@AndrewMwakibinga I'll resolve this conflict - the Postman stuff can be wonky with multiple users :/

authors: AndrewMwakibinga aeksco

repo: rcos/observatory-server


text:
fix: remove circular dependency warnings when generating bundled ts file

Fixes circular dependency warnings when running yarn build

Test Execution Failed.

Test Execution Passed.

:tada: This PR is included in version @lightningjs/ui-components-v2.20.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: rdkcentral/Lightning-UI-Components


text:
CTABs behave differently than before regarding stereo

Description:
MarvinJS CTABs no longer resolve to stereo smiles.
Two CTABs, one generated by MARVIN and the other edited to add the '2D' descriptor behave differently.  The first shows no stereo information (this is a change from previous rdkit versions) the latter shows stereo.
Output by Marvin

  MJ150720

  9  9  0  0  0  0  0  0  0  0999 V2000
    2.5687   -0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    2.1562    0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    2.5687    0.7144    0.0000 O   0  0  0  0  0  0  0  0  0  0  0  0
    1.3312    0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.9187   -0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.0937   -0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
   -0.3187    0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.0937    0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.9187    0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
  2  1  1  6
  2  3  1  0
  2  4  1  0
  4  5  2  0
  5  6  1  0
  6  7  2  0
  7  8  1  0
  8  9  2  0
  9  4  1  0
M  END

Stereo works with the 2D identifier

  MJ150720          2D

  9  9  0  0  0  0  0  0  0  0999 V2000
    2.5687   -0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    2.1562    0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    2.5687    0.7144    0.0000 O   0  0  0  0  0  0  0  0  0  0  0  0
    1.3312    0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.9187   -0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.0937   -0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
   -0.3187    0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.0937    0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
    0.9187    0.7144    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
  2  1  1  6
  2  3  1  0
  2  4  1  0
  4  5  2  0
  5  6  1  0
  6  7  2  0
  7  8  1  0
  8  9  2  0
  9  4  1  0
M  END

It looks like the default is now the coords get labelled as 3D by default in the conformer and it used to be 2D.

I think we should adopt the V3000 conventions
3D really means 2D
2D means 2D unless there are non-zero z coords
and nothing means 2D (unless there are non-zero z coords)

I will take a look tomorrow morning and figure out what’s going on

authors: bp-kelley greglandrum

repo: rdkit/rdkit


text:
Issue--ValueError: Depict error: Substructure match with reference not found.

from rdkit.Chem import Draw
from rdkit.Chem import AllChem
import matplotlib.pyplot as plt
smi=[
'COC1=C(C=CC(=C1)N5(=O)(=O)C)C2=CN=CN3C2=CC=C3',
'C1=CC2=C(C(=C1)C3=CN=CN4C3=CC=C4)ON=C2C5=CC=C(C=C5)F',
'COC(=O)C1=CC2=CC=CN2C=N1',
'C1=C2C=C(N=CN2C(=C1)Cl)C(=O)O'
]
template = Chem.MolFromSmiles('c1nccc2n1ccc2')
AllChem.Compute2DCoords(template)
mols=[]
for smi in smis:
mol = Chem.MolFromSmiles(smi)
AllChem.GenerateDepictionMatching2DStructure(mol,template)
mols.append(mol)
img=Draw.MolsToGridImage(mols,molsPerRow=4,subImgSize=(200,200),legends=['' for x in mols])
plt.imshow(img)
plt.show()
Raise ValueError: Depict error: Substructure match with reference not found.
I am a beginner at this, and I am not very familiar with the module.
Does that error means the substructure is not in molecule? How shall I solve it? thx!

Firstly, this is a question, not a bug, so should be in the Discussions tab rather than the Issues.
Secondly, can you please repost the code within three backticks so the formatting is preserved.  See
a comment at the bottom of https://github.com/rdkit/rdkit/discussions/6691 for a picture of what that means.
Thirdly, I expect you’re correct that the error message means the problem is at the generate depiction from 2D step.

已收到。小邮会以最快的速度用紧箍咒艾特主人。

Hi, I faced the same problem. Have you fixed it?

已收到。小邮会以最快的速度用紧箍咒艾特主人。

authors: DavidACosgrove GrailWang yanz-24


text:
Decouple questions from catalogs and make catalogs composable

Rationale / Begründung
An Editor would like to be able to compose a new catalog by re-using individual questions of the instance.
This would be helpful for the creation of specific catalogs for joint research projects.
Propositions
All questions of a RDMO instance should be listed under /questions/ and be filterable for URI.
A new catalog could be composed by choosing questions and sections from this list.
An alternative option set can be defined so that the questions can be re-used more easily and the copying of a complete catalog is not required.
At the creation of a new catalog, tests can be run to check if all the required attributes cover the views.
References / Verweise
Issues about the management backend:

https://github.com/rdmorganiser/rdmo/issues/361
https://github.com/rdmorganiser/rdmo/issues/158
https://github.com/rdmorganiser/rdmo/issues/534

In principle this should be the case for all nested elements: Sections, Question sets, Questions, and Options. Need major refactoring though.

+1 for this feature

@MyPyDavid At the creation of a new catalog, tests can be run to check if all the required attributes cover the views. I think this sentence deserves a new issue. This means that a view should be able to "scan" itself to check if all attributes in this view are present in a given catalog, right? (Or vice versa, a catalog should be able to tell if it can fill a view.)

yes, think this is a separate issue/feature. Is more of a part View and Catalog validation function..
I'll make a new one for it and remove it here.
DE text from this sentence:

Bei der Erstellung eines Katalogs kann geprüft werden, ob alle notwendigen Attribute für die Ansichten abgedeckt werden, ggf. wird angezeigt, welches Attribut bzw. welche dazu passenden Fragen noch genutzt werden können, um eine bestimmte Ansicht abzudecken.

From discussion:
Conceptually, the URIs need to be renewed or redefined.
When Questions or Questionsets are copied/used in multiple different Catalogs they need to keep their own unique ID (now knowns as URI) to be able to be used across RDMO instances.
Options:

change the key definition part of the URI  to contain eg Catalog/Page/Section/Questionset (A/B/C/D)

need to allow / in the key

change the URIs to an opaque UUID

requires a lot of migrations overhead and does not work with existing

allow the key or URI to be set manually

to be continued..

the elements have now models.ManyToManyField with each other
closed by 2.0.0

authors: MyPyDavid ikostadi jochenklar

repo: rdmorganiser/rdmo


text:
Add font-size

Hello, here's my PR that allow changing widgets text size.
I needed it to create a smaller UI.
How to use:
<a-gui-button
    width="2.5" height="0.75"
    onclick="testButtonAction" key-code="32"
    value="test button X"
    font-family="Arial"
    textsize="25px"
    margin="0 0 0.05 0"
>

That's it.
Also I would like to know if the toggle events (check and uncheck) that I added are in the correct PR.
I can remove them if you want, to make a new PR that be focused on new events.

Merged your font-size PR  - we should start thinking about not using px but dmm for VR
see:
https://sizecalc.com/#distance=55.17inches&perceived-size=660.0000547800046dmm&physical-size-units=inches
@matEhickey - Let me know if you are up for the math :-)

Indeed I was not very satisfied with this proportion unit, that why I left the "px" in the string.
Good idea, I totaly forgot about dmm unit, I'll try to implement this when I'll get time, shouldn't be too long.


text:
seems like img tag not working

.net core version: 1.0.4
dinktopdf: 1.0.8
I am trying to add an  but it seems it does not work.
I already have app.UseStaticFiles();
I added the image in my wwwroot folder
I also tried it on 2.0.2 version of dotnet
I already have the .dlls in my root folder
A snippet of my code
public IActionResult Pdf()
{
    var converter = new SynchronizedConverter(new PdfTools());
    var doc = new DinkToPdf.HtmlToPdfDocument()
    {
        GlobalSettings =
        {
            ColorMode = DinkToPdf.ColorMode.Color,
            Orientation = DinkToPdf.Orientation.Landscape,
            PaperSize = DinkToPdf.PaperKind.A4Plus,
        },
        Objects =
        {
            new DinkToPdf.ObjectSettings()
            {
                HtmlContent = "",
                WebSettings = { DefaultEncoding = "utf-8" },
             }
            }
        };

    var pdf = converter.Convert(doc);
    return File(pdf, "application/pdf");
}

How can I add an image to my page then convert it to pdf?
Cheers

Please check this issue . When I give absolute path to img tag it works as expected:
<img src='http://localhost:5000/guide.jpg
If you need relative path please check issues on wkhtmltopdf page.

Thank you! It worked! Now, I only need to configure environment variables

you can use HtmlAgilityPack to fix this issue
var htmlDoc = new HtmlDocument();
htmlDoc.LoadHtml(htmlContent);
foreach (var node in htmlDoc.DocumentNode.SelectNodes("//img"))
{
var src = node.Attributes[@"src"].Value;
if (src.StartsWith("/"))
node.SetAttributeValue("src", baseUrl + src);
}
            var newHtml = htmlDoc.DocumentNode.WriteTo();

authors: Mohemmad-Al-bughdadi cnceniza rdvojmoc

repo: rdvojmoc/DinkToPdf


text:
Allow null routes

When creating dynamic Routers there is a possibility to have null children.Hence null routes

👍
I've run into cases where I wanted to do this as well and found I couldn't.

Different PR added this too, thanks!
4b04d8ba3113db5f7f74d43075e5eb83b3146133

authors: Psiablo ryanflorence zenios

repo: reach/router


text:
Can't start web-client on Windows

-> yarn start

yarn run v1.22.4
$ SKIP_PREFLIGHT_CHECK=true react-scripts start
'SKIP_PREFLIGHT_CHECK' is not recognized as an internal or external command,
operable program or batch file.

I'll install cross-env as a dev dependency to enable this

ouch, not a windows user 😞

However we won't likely accept that PR. Please use bash on windows.

Hmm. Could this be a detractor for newcomers?

I won't speak for the whole team, but that's an awkward dependency to toss in that will touch all of our build scripts, ci/cd, pipelines etc, and some commands run after dev pruning. The impact is not minor.

I agree with you. I'll install and close the issue if there are no issues with that

So, I'm still not able to run the app without the cross-env package. I will try again tomorrow.
In Windows, to set a Global Variable in a command I need to run set SKIP_PREFLIGHT_CHECK=true, as opposed to just SKIP_PREFLIGHT_CHECK=true. What cross-env does is to abstract us from doing this.
If someone has experience with this I would very much thank you for your help. This is frustrating :/

I agree that cross-env would help in this manner, but am worried about adding it. I'd leave this question with the other leads (@s0, @wr46 @comoser). They should be able to help out with some advice. I've never had this problem (always ran Linux for dev on Windows)

Opened #168 to see if this solves it. Assuming everyone has docker engine installed. And I know the docker engine works differently on windows, so it may need some kind of adaptations

Thank you @comoser. Nonetheless, I was a bit too tired yesterday to follow through the whole installation of the Linux subsystem on Windows. I'm trying out this morning and will give you guys some feedback

I have installed successfully Ubuntu in Windows and I'm able to run this now. I will close this issue.
Thanks guys!

authors: comoser puzzledbytheweb sabind


text:
Nested Navigations populating the root navigator

I have a strange Problem which could  be Duplicate by other issues. Since my setup is very complex (although i just thing it's a normal setup if you have a bigger application) i create a new issue.
I was able to solve my problem, but i think it's possible a side effect that it works and maybe some changes in the future might break it. Therefore i present the problem i want to solve and hopefully there will be a possible solution for it or at least the workaround will not be broken in the future.
We have a react native application with deeply nested Navigations. (Stack-Tab-Stack-Tab-Stack... You get the picture).
I need a Main Header over everthing (because that's the world works), a Main Bottom Tab Navigation and within those Tabs is again a StackNavigation for multiple Screens within this Tab.
In one case i also have another TabNavigation.
Now each of this deepest TabNavigation Screen needs to update the Header with it's title and headerRight Buttons.
The setup that i ended up was that each Screen within that TabNavigation needed to have another StackNavigator. Then i needed a Root StackNavigator which hold the main BottomNavigation TabNavigation. I add a quick example, ignore the Syntax, it's just to get a better picture:
root = stackNavigation({
  mainTabs = TabNavigation{
    mainTabA = stackNavigation{ ..},
    mainTabB = stackNavigation{
        ...
        pageFour = TabNavigation({
            pageTabA = stacknavigation{
                Foo: {
                   screen: Foo,
                   navigationoptions: () => {
                      headerRight: (< MyIcon />)
                   }
                }
            },
       },
    }
}, { headerMode: 'none' })

Strangely if you add a root Header and hide it and don't setup any StackNavigatorConfig the configuration of the deepest StackNavigation Screen is handover to the top. As soon as any general configuration is done within any of the StackNavigation it's lost.
I ended up setting all style Options and everything for each screen of my application. It works, but is far from a good solution. And it's volatile since i have no idea why it works and it looks like it's a side effect which can be broken at any time.
I really would like to end up with less stacknavigators which i have for the Header Configuration. I would need to be able to configure the main Header within each screen, no matter if it's a tab or a stack.
Maybe a rootNavigationOptions configuration? Just a thought.
If you read to this line, thank you. I really appreciate it.

Hi! In an effort to reduce the number of open issues I'm closing issues that haven't had any activity in a while.
If you think this should be re-opened please let me know or, if you can, re-open it.
If this is a question please consider asking it on StackOverflow (react-navigation)
Thanks!

Still an issue

authors: dready manubamba spencercarli

repo: react-community/react-navigation


text:
how to style the tab icon/label if the tab is actually a secondary nested tab navigator

Styling tab icon/label is easy for a class as a tab, but what if the tab is another nested tab navigator?

If your tab is another navigator, you can:
TabNavigator({
   MyTab: {
     screen: TabNavigator({}),
     navigationOptions: {
       // style tab here
     },
   },
})


text:
Currently a user can double click on a button while an animation is i…

Currently a user can double click on a button while an animation is in progress resulting in the same navigation call getting triggered twice.  This prevents duplicate navigation to the same route.

-1 #135 has some other ideas on how to solve this issue, and this PR would break react-navigation in some cases
This PR rejects all actions where routeName matches the current routeName whether unintentional or intentional. (and seems to do it across multiple levels of navigator)
However there are a wide variety of situations where an app may intentionally desire navigating to another route with the same name, notably the same routeName but different params. eg: You're on { routeName: 'Profile', params: { user: 'Alice' } } and a friend link to "Bob" wants to navigate to { routeName: 'Profile', params: { user: 'Bob' } }. This PR would reject that.

It looks like #135 is a lot of talk without anything happening.  I'd be happy to close this PR if there is another solution incoming.
If not, I'd be happy to add support for checking params.  That is easy enough to do.
Let me know what you guys are planning.

Checking for params just sounds like stacking a hack on top of another hack to work around the flawed nature of the hack. You're now doing a shallow/deep comparison of objects (which this lib doesn't do) just to work around something that there are better ways of handling.
If you want to work around this now, you don't even need any changes to react-native. Just set a this._lock = true; in your event handler when you make the navigate call, reject any events while this._lock is true, and unset that after a few seconds. Or use a debounce function from a library like lodash.

I agree that this is a hack solution.  However, having to do tracking of this._lock = true outside of react-navigation is also a hack (a worse one in my opinion).  This issue should be handled inside the library.
I'll leave this PR open for now so that others may reference it until a more elegant solution is implemented.

I'm going to mark this PR as "On Hold" for now. There has been discussion on this enhancement at https://github.com/react-community/react-navigation/issues/135, https://github.com/react-community/react-navigation/issues/271, and https://github.com/react-community/react-navigation/pull/1787. I think that this is a much needed part of the library; however, we should be careful to accept any "hack" solutions. A hack is better than no solution, in my opinion, but I'm curious what you think @skevy

Yeah, I've been following some of the other discussions and I 100% agree that this should not be merged.  There are much better solutions coming.

you can handle this now with idempotent pushes, still need to write up docs here: https://github.com/react-navigation/react-navigation.github.io/issues/42 though!
this.props.navigation.navigate({routeName: 'yourRoute', key: 'pick-a-key'}); -- it will only navigate to that once (based on key) regardless of how many times you fire it

authors: brentvatne dantman ghuh matthamil


text:
Custom input — change DayPickerSingleDateController's visible month when date changes

Hi,
I have a set up with my own custom input which allows user to type the date string in the preferred format. If the date string is valid — <DayPickerSingleDateController /> is then used to preview the typed date (or to select the date from the calendar). The problem is when the user types the date that's out of the range of the visible month then <DayPickerSingleDateController /> does not re-render itself and I've got no 'preview'.
There is an initialMonth prop which takes the function and uses it to set the calendar to preferred month on component initialization, but after that function won't be invoked. Is there a way to force <DayPickerSingleDateController /> to change the visible month every time the date changes?
I was able to fix my problem with commenting out
https://github.com/airbnb/react-dates/blob/master/src/components/DayPicker.jsx#L197
and https://github.com/airbnb/react-dates/blob/master/src/components/DayPicker.jsx#L238 so that hasSetInitialVisibleMonth is never true, therefore <DayPicker /> runs initialMonth function every time it renders, but probably that's not the most elegant way to solve the problem.
Am I missing something here?

hi @volodymyr-kushnir did you find any hack for this one?

Hey @achtan, no, no, I didn't. As I said in my first post — you can workaround the problem by commenting out hasSetInitialVisibleMonth so that it'll always be false and that will force the calendar to re-render itself every time the date changes.
I couldn't decide on whether this is a flaw in the library that has to be fixed or simply an edge case scenario that shouldn't affect the design of the library — so instead of forking the react-dates I switched to react-day-picker for the time being.

Hi @volodymyr-kushnir, initialVisibleMonth currently only updates the month when the calendar is closed and then reopened. The reason for this is that we don't currently have a solution for handling the animation if you wanted to say, navigate 10 months into the future. This is something we're def still looking to solve.

I've run into the need to snap the calendar in the DRP to a certain date range, as described in #931 and #929. Seems to me that both these issues require solving it first for the SDP, as described here by OP.
@majapw, you mentioned above that the solution would require an animation for navigating more than a single month at a time.
So I thought I'd suggest the animation used by the folks at Google Calendar, who solved this nicely by a left/right shift followed by a quick fade out and in.
Maybe someone would be ready to take on this challenge if the maintainers expressed interest in a PR.

Higher quality: https://imgur.com/a/Mheqg

I was able to get a workaround for this by changing the key of the component whenever I want to change the month, which forces a re-mount. It would be great to see this issue solved so we don't have to rely on these hacky ways to go about this :)

Running into the same issue for the DRP. I've updated from v12 to v16 and now I'm seeing a glitch when switching the start date (to another month not visible). I'm using the key approach to force a re-mount, it wasn't an issue on v12 but it is now on v16.
Would that be related to react-with-styles (wild guess) ? I have the same issue on v13 and that was the only change I've seen there 🤔
Any workaround to prevent the glitch on change ?

Any news about this?

@jabsatz Could you elaborate more on how you achieved that by changing the key please?

It was a while ago, but if you update initialVisibleMonth and change the key at the same time, you force the component to re-mount with the "initial" month as the "current" month. What you use as a key is up to you, I think I used an additive (0,1,2...), but you could really use anything as long as it's different from your previous key.

@jabsatz I'm sorry I'm not exactly able to follow your solution. I don't know how I'll update my key in response to my date getting selected along with updating the initial visible month. Also, I did not get why it will re-mount if I change the initialVisibleMonth and the key at the same time. Could you show an example of how you implemented it? A snippet, perhaps? Also, thanks for the answer!

This feature would be very useful

Any updates about this?

authors: achtan andrejunges burtyish ignaciosantise jabsatz khanilov majapw pedroabreu swaritkohli volodymyr-kushnir

repo: react-dates/react-dates


text:
Drop from outside doesn't work on iPad

At first, thanks for your support and your incredible work in this awesome library...
The problem (maybe bug):
onDragStart and onDragStop events currently is not fired on iPad under iOS 13.3 and this functionality doesn't work.
It considers like a bug? I think so.
What can I do?
Thanks in advance.

How can we access source element attr onDrop?

You can find more about data transfer here
onDragStart={e => {
          e.stopPropagation();
          this.dragImage = this.createDragPreview(this.props.text);
          // you need line below in your droppable outside element
          e.dataTransfer.setData("text/plain", JSON.stringify(this.props.transfer));
          e.dataTransfer.setDragImage(this.dragImage,0,0);
        }}
onDragEnd={e => {
          e.stopPropagation();
          e.dataTransfer.setData("text/plain", "");
          e.dataTransfer.clearData("text/plain");
          if(this.dragImage)
            document.body.removeChild(this.dragImage);
}}

And then retrieve data in onDrop property
onDrop={(value : any) => {
    // TODO on drop
    let drop : any = {
      x : value.x,
      y : value.y,
      h : value.h,
      w : value.w,
      // this is what you need
      transfer : JSON.parse(value.e.dataTransfer.getData('text/plain'))
    }
}}

Hope it goes well for you. But the main problem of this topic continues working bad, I mean, drag from outside doesn't work on ipad! Please someone can help me?

In addition I tried to use a Polyfill that handles this event properly on iPad but it seems to produce another error... It can retrieve x, y, h, w after apply Polyfill.
Someone solve this with another solution? Maybe this awesome library must consider fix this on iPad?

Someone could say something about?

Nobody with the same issue?

I can't believe nobody has the same problem here! Please @STRML say something about...

Your problem is that the "drag n' drop" feature native in HTML5 (with a bit of JavaScript) is not supported by most mobile browsers. Click here for a list of what is supported.
I suggest using an alternative approach that supports all mobile browsers. See this link with more explanation: https://medium.com/@deepakkadarivel/drag-and-drop-dnd-for-mobile-browsers-fc9bcd1ad3c5

Your problem is that the "drag n' drop" feature native in HTML5 (with a bit of JavaScript) is not supported by most mobile browsers. Click here for a list of what is supported.
I suggest using an alternative approach that supports all mobile browsers. See this link with more explanation: https://medium.com/@deepakkadarivel/drag-and-drop-dnd-for-mobile-browsers-fc9bcd1ad3c5

Thanks for your response, but...
This feature would be part of this library because it implements onDrop Prop which actually takes and transform dataTransfer property from a draggable HTML5 element. That means is the only way to reorganize the grid. If you use an external library to handle drag and drop, from outside, the grit will not reorganize according where you dropped the new element.
I suggest this library may support drag and drop functionality to all browsers. Or reimplement his onDrop Prop in order to handle dropped element position and reorganize grid.

You are welcome to submit a PR if this is something you would like.
On Tue, Jun 2, 2020, 5:48 AM José Sánchez Aranda notifications@github.com
wrote:

Your problem is that the "drag n' drop" feature native in HTML5 (with a
bit of JavaScript) is not supported by most mobile browsers. Click here
https://caniuse.com/#feat=dragndrop for a list of what is supported.
I suggest using an alternative approach that supports all mobile browsers.
See this link with more explanation:
https://medium.com/@deepakkadarivel/drag-and-drop-dnd-for-mobile-browsers-fc9bcd1ad3c5
Thanks for your response, but...
This feature would be part of this library because it implements onDrop
Prop which actually takes and transform dataTransfer property from a
draggable HTML5 element. That means is the only way to reorganize the grid.
If you use an external library to handle drag and drop, from outside, the
grit will not reorganize according where you dropped the new element.
I suggest this library may support drag and drop functionality to all
browsers. Or reimplement his onDrop Prop in order to handle dropped element
position and reorganize grid.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/1180#issuecomment-637426789,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJEKP4QLINTLSC4BT2R64TRUTDIFANCNFSM4LY4CQQQ
.

same issue :( not working in mobile

I'm having same issue. I have applied a Polyfill here https://github.com/timruffles/mobile-drag-drop but iit's not compatible with this react grid library. @josesaranda did you overcome it?

Your problem is that the "drag n' drop" feature native in HTML5 (with a bit of JavaScript) is not supported by most mobile browsers. Click here for a list of what is supported.
I suggest using an alternative approach that supports all mobile browsers. See this link with more explanation: https://medium.com/@deepakkadarivel/drag-and-drop-dnd-for-mobile-browsers-fc9bcd1ad3c5

Thanks for your response, but...
This feature it would be part of this library because it implements onDrop Prop which actually takes and transform dataTransfer property from a draggable HTML5 element. That means is the only way to reorganize the grid. If you use an external library to handle drag and drop, from outside, the grid will not reorganize according where you dropped the new element.
I suggest this library must support drag and drop functionality to all browsers. Or reimplement his onDrop Prop in order to handle dropped element position and reorganize grid without use dataTransfer.

How large of a task would this realistically be to reimplement onDrop to not use dataTransfer? I'd be interested in making a PR for this but want to get a guess for the size.

In addition I tried to use a Polyfill that handles this event properly on iPad but it seems to produce another error... It can't retrieve x, y, h, w after apply Polyfill.
Someone solve this with another solution? Maybe this awesome library must consider fix this on iPad?

For anyone coming here for the solution,
As said above, whenever polyfill is used, the dropped item has coordinates as x: NaN and y: NaN.
Just add default dropping coordinates in onDrop handle like x: 0 and y:0 before updating your layout array.

In addition I tried to use a Polyfill that handles this event properly on iPad but it seems to produce another error... It can't retrieve x, y, h, w after apply Polyfill.
Someone solve this with another solution? Maybe this awesome library must consider fix this on iPad?

For anyone coming here for the solution,
As said above, whenever polyfill is used, the dropped item has coordinates as x: NaN and y: NaN.
Just add default dropping coordinates in onDrop handle like x: 0 and y:0 before updating your layout array.

@SkrewEverything Could you elaborate a bit more? I am unsure about the way to proceed.
Is there a way to make it work on iOS/iPadOS?

authors: STRML SkrewEverything akshaygoyal88 hugolgst josesaranda phongtran-uit phucluke polyrain

repo: react-grid-layout/react-grid-layout


text:
[react-native-windows] Missing Publisher Details in the details tab under dll Properties

The CheckboxWindows.dll is missing versioning/publisher details set in their metadata.
Currently, the publisher information is not available in the properties (screenshot below), and this absence of publisher details is causing issues with AppLocker (a security tool). AppLocker can sometimes block updates to DLLs if they do not have proper versioning/publisher details set in their metadata.

Thanks for your PR


text:
Fix blur style type

This way, we can use the results from StyleSheet.create

Fixed in #288.


text:
Too much releases

It's a bit annoying having releases so often. Can you wait to have a couple of commits to release a new version?
When everything's important, nothing is.

OK. I got that.

@magicismight nice! awesome work anyway 👍

Just keep bumping!

authors: magicismight neiker sibelius

repo: react-native-community/react-native-svg


text:
[WIP] Fix android subtitle issue caused by using rawdatasource

I could reproduce the issue described in #1371 and fixed the issue. I'm not sure if this breaks some other functionality.
When testing, I received the following error message:
E/ExoPlayerImplInternal( 5534): Source error.
E/ExoPlayerImplInternal( 5534): com.google.android.exoplayer2.upstream.RawResourceDataSource$RawResourceDataSourceException: com.google.android.exoplayer2.upstream.RawResourceDataSource$RawResourceDataSourceException: URI must use scheme rawresource

Tested on Android Emulator API 28 and 18. Release and Debug builds.
Project used: https://github.com/reime005/VideoPlayerTest
Fixes issue #1371

@reime005 I see you've got a WIP tag on this and don't want to test / merge until you give the go ahead. Do you want to do any more testing before I test and merge this?

Works great! Thanks so much for tracking this down and fixing it.


text:
expo 34 error, Invariant Violation: requireNativeComponent: "RNCWebView" was not found in the UIManager.

Bug description:
use Expo v34 and react-native-webview 7.0.1, Invariant Violation: requireNativeComponent: "RNCWebView" was not found in the UIManager.
Expected behavior:
Screenshots/Videos:

Environment:

OS: MacOS
OS version: 10.14.6
react-native version: https://github.com/expo/react-native/archive/sdk-34.0.0.tar.gz
react-native-webview version: 7.0.1

Your should cd in iOS directory and "pod install",  then run the iOS workspace, it will be ok.

Your should cd in iOS directory and "pod install", then reopen the iOS workspace and run it.

I use creat-react-native-app init project, not ios directory.

I have the same problem

If you are using expo, you have to wait till expo updates his sdk because @Titozzz changes are native
@Titozzz  explained his changes in a expo thread: https://github.com/expo/expo/issues/5497

Thanks @WhatzzUp you are 100% right. Can't use this directly, you need to wait for expo to pull the changes in, (or you can eject but prob not what you are looking for)

Same problem. Re-install pods don't help. Has anyone found a solution?

Thank @wanghe826
In my case, Your solution helped me.
I tried to use react-native-azure-ad-2.
Then I used AzureLoginView to sign in with Microsoft.
And I faced this issue.
You saved my life.
Thank you

Im facing this issue with expo 35.


text:
Fix #48

#48

Done all this problem.

@tstariqul, Fix already made.
Duplicate of #49

repo: react-native-elements/playground


text:
Removes one or more tracks from the queue

Describe the bug
It doesn't anything.
react-native-track-player@2.0.0-rc13
To Reproduce
Steps to reproduce the behavior:

Select the Track Object
Trying to remove the current Tracks
Add the new Tracks object

Environment (please complete the following information):
System:
    OS: macOS 10.15.2
    CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
    Memory: 60.51 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.4.0 - /usr/local/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 23, 24, 25, 26, 27, 28
      Build Tools: 23.0.1, 23.0.3, 25.0.0, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.2, 28.0.3
  IDEs:
    Android Studio: 3.6 AI-192.7142.36.36.6392135
    Xcode: 11.3/11C29 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.13.1 => 16.13.1
    react-native: 0.61.5 => 0.61.5
  npmGlobalPackages:
    react-native-clean-project: 3.2.4
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7

**Code - EDITED **
let arrayTracksIds = []
const tracksEmFila = await TrackPlayer.getQueue();

for (let i in tracksEmFila) {
            arrayTracksIds.push({
                id: tracksEmFila[i].id,
                url: tracksEmFila[i].assetUrl96
            });
        }
await TrackPlayer.remove(arrayTracksIds);

Would you have time to test trying the same thing within the example app on ‘dev’? (1.2.x)

@curiousdustin, sure. I'll do that

Also which platform(s)?

Android, for now

The example app is making its normal ritual... downloading this, download that ... gradle build whatever ... Meanwhile, how can I clear the queue without using reset()?

I think you just need to pass an array of string IDs instead of objects.

The docs may need improvement on this method.

I did it in first place but crash my app. When I tried passing an object just do nothing ...

I’m on mobile right now but I’m pretty sure it should be just string IDs.
Can you provide the error for the crash?

That's the hard thing... My app just close.
By the way, when I tried run the example app, i got this error:
Loading dependency graph...(node:68361) UnhandledPromiseRejectionWarning: Error: jest-haste-map: Haste module naming collision:
  Duplicate module name: react-native
  Paths: /Users/celiogarcia/dev/lolo/example/node_modules/react-native/package.json collides with /Users/celiogarcia/dev/lolo/example/node_modules/react-native-track-player/example/node_modules/react-native/package.json

This error is caused by `hasteImpl` returning the same name for different files.

For that error try removing the example node modules and installing again.
You can use android studio logcat, or log at in a terminal, to see the crash error.

Okay... It's now 02:43 am. I so tired. I'll look for it late. Thanks for your support sor far

@curiousdustin , if I remove the example node_modules anda installing again I'll cannot  run metro bundler

Never mind. I removed the example folder inside on node_modules/react-native-track-player

My approach was wrong thats why when I passed an array of ids crashed my app. After testing on example app I realized how bad I was doing it.
Thats all fine. I'll closed this issue.
Thanks. ;)

@curiousdustin , I have to reopen this issue because its still crash the app. I used the same code on my project that I used on example app.
The logcat tell me that:

2020-04-24 13:48:22.834 10103-10103/com.toquemedia.toqueplay E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.toquemedia.toqueplay, PID: 10103
    java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
        at java.util.ArrayList.get(ArrayList.java:437)
        at java.util.Collections$SynchronizedList.get(Collections.java:2461)
        at com.guichaguri.trackplayer.service.player.ExoPlayback.onPositionDiscontinuity(ExoPlayback.java:271)
        at com.guichaguri.trackplayer.service.player.ExoPlayback.onTimelineChanged(ExoPlayback.java:262)
        at com.google.android.exoplayer2.ExoPlayerImpl$PlaybackInfoUpdate.lambda$run$0$ExoPlayerImpl$PlaybackInfoUpdate(ExoPlayerImpl.java:790)
        at com.google.android.exoplayer2.-$$Lambda$ExoPlayerImpl$PlaybackInfoUpdate$N_S5kRfhaRTAkH28P5luFgKnFjQ.invokeListener(Unknown Source:2)
        at com.google.android.exoplayer2.BasePlayer$ListenerHolder.invoke(BasePlayer.java:165)
        at com.google.android.exoplayer2.ExoPlayerImpl.invokeAll(ExoPlayerImpl.java:823)
        at com.google.android.exoplayer2.ExoPlayerImpl.access$000(ExoPlayerImpl.java:43)
        at com.google.android.exoplayer2.ExoPlayerImpl$PlaybackInfoUpdate.run(ExoPlayerImpl.java:787)
        at com.google.android.exoplayer2.ExoPlayerImpl.notifyListeners(ExoPlayerImpl.java:726)
        at com.google.android.exoplayer2.ExoPlayerImpl.updatePlaybackInfo(ExoPlayerImpl.java:701)
        at com.google.android.exoplayer2.ExoPlayerImpl.handlePlaybackInfo(ExoPlayerImpl.java:648)
        at com.google.android.exoplayer2.ExoPlayerImpl.handleEvent(ExoPlayerImpl.java:598)
        at com.google.android.exoplayer2.ExoPlayerImpl$1.handleMessage(ExoPlayerImpl.java:126)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:201)
        at android.app.ActivityThread.main(ActivityThread.java:6815)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

You are using the same version in the example and in your app?
You are saying the same basic process works in the example app, but not in yours?
Are you able to crash the example app with similar code?

I'm using RNTrackPlayer 2.0.0-rc13 with RN 0.61.5 and same basic process works in the example app. For now, I'm using TrackPlayer.removeUpcomingTracks() and working as I expected when used TrackPlayer.remove()

Are you also testing in the example from the same version: 2.0.0-rc13?
Does your last statement means you are using both of these in order, and it does not crash anymore?
TrackPlayer.removeUpcomingTracks()
TrackPlayer.remove([id1, id2, id3])

Noup. My last statement is:
await TrackPlayer.removeUpcomingTracks()
await TrackPlayer.add(newTracks);

The IndexOutOfBoundsException error you mentioned is #661, which is fixed by #778, which has not been included in a v2 release yet.

authors: curiousdustin ithustle


text:
[Android] Use root project's sdk versions if specified

This is a popular strategy for react native plugins and fixes several issues. I recently upgraded react native and the default sdk for react native 0.58.4 is 28. Rather than updating it manually in RNTP, I suggest using whatever sdk is being used in the parent project. For my purposes, RNTP seems to work fine with 28. Projects still on 27 are not affected by this change.
Also, each sdk has a default build tools version associated with it. Sometimes the buildToolsVersion setting is completely ignored if it doesn't match the sdk. There's no need to set it.

LGTM. Thank you.

authors: Guichaguri timmywil


text:
[Discussion] Consider using depfu for dependency updates

Quick synopsis:
Depfu is a service that keeps track of your projects dependencies and (based on your rules)
automatically opens PRs and thus would run the travis ci tests.
https://depfu.com/for-open-source
It is free for open source projects.

@kristfal, did you have some time to look at this?
We have quite some dev dependencies, this would definitely ease the pain of updating them.

Hey, I will. I’m unavailable for the this and the next week. Once I’m back, I’ll land this and migration (one way or another). Thanks for raising.

Thanks for this tip. Closed via #93.

authors: ferdicus kristfal

repo: react-native-mapbox/maps


text:
MapView-check if screen region is displayed

Question
Is there a way to check if current screen region is loaded/visible? I have tried to use onMapReady prop but it seems that it doesn't wait for map to be visible.
I'm trying to find a way how to take a snapshot on initial render, as soon as map (current screen region) becomes visible.

There is a property that checks is map/tiles are loaded before calling a callback. (With typescript onMapLoaded type is missing, therefore it displays prop as if it does not exist)
<MapView
  onMapLoaded={() => console.log('MAP LOADED')}

  /**
   * Callback that is called once all tiles have been loaded
   * (or failed permanently) and labels have been rendered.
   */
  onMapLoaded: PropTypes.func,

repo: react-native-maps/react-native-maps


text:
Expo SDK 48 iOS build failed: "Cannot add Google Maps to the project's AppDelegate because it's malformed"

Summary
[stderr] Error: [ios.appDelegate]: withIosAppDelegateBaseMod: Cannot add Google Maps to the project's AppDelegate because it's malformed. Please report this with a copy of your project AppDelegate.
[stderr] Error: [ios.appDelegate]: withIosAppDelegateBaseMod: Cannot add Google Maps to the project's AppDelegate because it's malformed. Please report this with a copy of your project AppDelegate.
[stderr]     at /Users/expo/workingdir/build/node_modules/@expo/config-plugins/build/ios/Maps.js:218:19
[stderr]     at action (/Users/expo/workingdir/build/node_modules/@expo/config-plugins/build/plugins/withMod.js:201:29)
[stderr]     at interceptingMod (/Users/expo/workingdir/build/node_modules/@expo/config-plugins/build/plugins/withMod.js:105:27)
[stderr]     at action (/Users/expo/workingdir/build/node_modules/@expo/config-plugins/build/plugins/createBaseMod.js:61:27)
[stderr]     at async interceptingMod (/Users/expo/workingdir/build/node_modules/@expo/config-plugins/build/plugins/withMod.js:105:21)
[stderr]     at async evalModsAsync (/Users/expo/workingdir/build/node_modules/@expo/config-plugins/build/plugins/mod-compiler.js:204:25)
[stderr]     at async Object.compileModsAsync (/Users/expo/workingdir/build/node_modules/@expo/config-plugins/build/plugins/mod-compiler.js:124:10)
[stderr]     at async configureProjectAsync (/Users/expo/workingdir/build/node_modules/@expo/cli/build/src/prebuild/configureProjectAsync.js:54:15)
[stderr]     at async prebuildAsync (/Users/expo/workingdir/build/node_modules/@expo/cli/build/src/prebuild/prebuildAsync.js:83:9)
[stderr] error Command failed with exit code 1.

Reproducible sample code
This is a build time error

Steps to reproduce
Run expo EAS build: eas build --platform ios
Expected result
Build successfully
Actual result
Build failed
React Native Maps Version
1.4.0,1.3.2
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.71.2
What version of Expo are you using?
SDK 48
Device(s)
iPhone
Additional information
No response

Same here

Would it be appropriate for you to report it to Expo? https://github.com/expo/expo/issues/new?assignees=&labels=needs+review&template=bug_report.yml

Would it be appropriate for you to report it to Expo? https://github.com/expo/expo/issues/new?assignees=&labels=needs+review&template=bug_report.yml

Maybe with an reproducible example.
@TrustyTechSG Does the issue still persist? Can you create a minimal reproducible example and open an issue in the Expo Directory?

Would it be appropriate for you to report it to Expo? https://github.com/expo/expo/issues/new?assignees=&labels=needs+review&template=bug_report.yml

Maybe with an reproducible example.
@TrustyTechSG Does the issue still persist? Can you create a minimal reproducible example and open an issue in the Expo Directory?

I created an issue in the expo repository with a reproducible example.
This issue is only present when using Google maps for me

Would it be appropriate for you to report it to Expo? https://github.com/expo/expo/issues/new?assignees=&labels=needs+review&template=bug_report.yml

Maybe with an reproducible example.
@TrustyTechSG Does the issue still persist? Can you create a minimal reproducible example and open an issue in the Expo Directory?

I created an issue in the expo repository with a reproducible example.
This issue is only present when using Google maps for me

Awesome for the bug and example. Can you link the issue here as well?
For me it still persists.

This issue is fixed with @expo/config-plugins@6.0.1, we can close it maybe

https://docs.expo.dev/versions/latest/sdk/map-view/
Does this not work for you?

It should be fixed with the config plugin update.
In addition I had to remove the expo cli version from package.json

authors: RyanTG TrustyTechSG mariomurrent-softwaresolutions pchmn zaidoooo


text:
Chore/bump example rn to 0.74

Does any other open PR do the same thing?

No
What issue is this PR fixing?
It's just a bump of example app react-native version. I want to tackle new architecture support after merging this one.
How did you test this PR?

It affects both platforms but only our example application.
I have tested it on real device Android and iOS simulator.

Unfortunately I'm not able to fix pipelines for now because highest available xCode version in "macos latest" is 14.2, and there's an error that it requires 14.3. Other than that everything else should work fine.

@mateki0 thanks for your contribution here, two things:

Yes simply removing (fabricEnabled, newArchEnabled ...) seems like the right way to go, check out a new RN project using npx react-native@latest init AwesomeProject you will see that no such methods in the AppDelegate.

please remove the changes to the ci files / github actions, you can see clearly that macos latest image does include xcode 15.3 and even 15.4
https://github.com/actions/runner-images/blob/main/images/macos/macos-14-Readme.md
we might need an xcode-select step, see: https://stackoverflow.com/questions/65821440/how-to-select-xcode-version-in-fastlane-when-using-github-actions

but that's it.
tag me please once done so that we merge this :)

@mateki0 branch is outdated, please rebase

@salah-ghanim done


text:
Modal don't show

I have a question. when my app is foreground, I would show a modal, then the background modal will close, but I using appState, the modal doesn't show. How i can show a modal when the app is foreground ?? like paypal

it's not modal. You can see instructions and follow:
https://jonaskuiler.medium.com/creating-a-security-screen-on-ios-and-android-in-react-native-97703092e2de
or use
rnbootsplash
hope this helps

@hoanglam10499 thanks :)))

repo: react-native-modal/react-native-modal


text:
TVMenuControl module isn't working with React Native Navigation.

So I have been working on a project using React Native Navigation and been seeing some problems with TVMenuControl Module for disabling and enabling (it's not working) I believe it's related to how React Native Navigation basically on every screen navigation sets that screen as the RootView.
I also noticed that the bridge is working fine but the issue might be with NSNotificationCenter it's not posting the notification.
React Native version: 0.62
Steps To Reproduce

Use React Native Navigation
Navigate to a new screen
call disableTVMenuKey it doesn't work

+1 to this

I have the same problem  @dlowder-salesforce

I'll have a look...  my first guess is that RNN is putting in its own gesture handler for the root view that is replacing the one used by react-native-tvos.

Ok this is not a bug.  I built a tvOS version of Wix's react-native-crash-course project (which uses React Native Navigation).... you can find it at https://github.com/dlowder-salesforce/react-native-crash-course-tvos/tree/tvos-0.62.2 .
Several dependencies (react-native-navigation, react-native-blur, react-native-ui-lib) required fixes for tvOS compilation errors.  I forked the repos and made the required changes, as you'll see in the package.json for the above sample project.
Once I got everything working, I see that the project exhibits correct behavior, without any need for TVMenuControl.  This is because RNN is pushing real native views onto a UINavigationController stack, so the menu key works natively without any special gesture recognizer needed.  Details are discussed at https://stackoverflow.com/questions/32663814/override-apple-siri-remote-menu-button-default-behavior .
So I'm happy to report that you don't need TVMenuControl at all :)

thanks @dlowder-salesforce, but I just want to mention that my issue isn't related to the navigation not working. the enableTVMenuKey and disableTVMenuKey aren't working properly. I have use cases in the project where I don't want the default menuKey behaviour and others where I do and the postNotification calls aren't working on the same screen when called from react native side.
postNotification isn't responding well and I think it's related to the way react native navigation is using multithreading somehow to set root views. but I am not sure, what I am sure of is that postNotification using things like disableTVMenuKey and enableTVMenuKey isn't working well.
again thanks for the help. it's much appreciated.

Thanks for explaining the actual issue that you're having.  I can reproduce this in the example project I created, and I'll reopen this and have a look.

على راسي يا ختيار. لسه فيك نفس تشوف

Even though I don't use RNN, for me this still seems to be an issue when using createNativeStackNavigator from react-native-screens/native-stack. I'm not quite sure if it is indeed related to the original issue mentioned here, but as react-native-screens also uses a native screen, it might be the same issue.
Whenever a screen is pushed, TVMenuControl.enableTVMenuKey(); has no effect anymore, and the screen is immediately popped again when pressing the tvOS menu button. So my BackHandler listener is ignored.
This is not an issue with the root screen of my navigation stack.
Any hint towards a solution would be much appreciated.
Tried this with:
react-native-tvos 0.63.4-0
react-navigation/stack 5.12.8
react-native-screens 2.17.1

I can get this to work by listening to RCTTVEnableMenuKeyNotification and RCTTVDisableMenuKeyNotification in react-native-screen's RNSScreenView and then adding RCTTVRemoteHandler's tvMenuKeyRecognizer to this view.
This prevents the UINavigationViewController to handle the event before it could be handled by RCTRootView.
However, this is just a hack in react-native-screen, so if there are better ideas out there, please let me know.

Just in case somebody else wants to use createNativeStackNavigator, I created a fork or react-native-screens to make TVMenuControl.enableTVMenuKey(); work with it:
https://github.com/fasci/react-native-screens

@fasci I've picked up this bug again, will keep you updated.  Thanks for the react-native-screens contribution!

Ok I've got a working demo app at https://github.com/douglowder/rnn-starter, that has current RNN fully working on tvOS.  In digging through the issues, I find the following:

RNN doesn't have to use react-native-screens, so a fix there will not work in all cases
If I run this app in "three_tabs" mode, it uses a bottom bar nav which is implemented as a UITabBar.  In this case, even the other TV events (up, down, etc.) don't show up.
Debugging the view hierarchy indicates that the place to hook into RNN is probably RNNStackController.

Continuing to investigate.

I've put together a fix for this.  It requires changes both here and in RNN (but RNN requires a lot of patches for tvOS anyway).  Creating a PR.

Fixed in release 0.64.2-4

@fasci see https://github.com/react-native-tvos/rnn-starter-tv/commit/6930e918b684d84288e1acea93aca530c9f72862 for the patches needed to make RNN work on TV.

Has anyone found a way to override the backHandler for tvOS with React navigation? enableTVMenuKey doesn't seem to work

I fixed my issue by referencing the sample code Sir Doug Lowder wrote here
I think what fixed it for me was to remove the "Native" stack API and use the non-native API that React Navigation has. I'm not entirely positive on that though. I can post my dependency versions if you want to compare.

Removing native stack and replace it with non-native fixt it for me! Ty @NickAVolpe !

authors: NickAVolpe RobertArissen ali-sao cnblackxp dlowder-salesforce douglowder fasci mahdi-hamdan

repo: react-native-tvos/react-native-tvos


text:
updated ReactVideoView.java to fix seeking issue on android

This PR fixes a bug when trying to seek in the Video component on Android. Before, the video would skip to the beginning of the video if the user tried to seek, but now it works as expected.
To test, simply use the video component on android, and you are now able to seek.

@monahans can you please use the constant ? "3" seems strange here, nobody will understand.
As sample there is already:
https://github.com/react-native-video/react-native-video/pull/2555/files
https://github.com/react-native-video/react-native-video/pull/2511/files

Updated to use MediaPlayer.SEEK_CLOSEST

When will the PR be in the latest beta release?

authors: freeboub khushal87 monahans

repo: react-native-video/react-native-video


text:
use 'screen' instead of 'window' when getting Dimentions

I created this pull request in favour of this issue: https://github.com/react-navigation/stack/issues/217
However I'm not sure if this will solve the issue after updating react-native-safe-area-view to v1.0 in this repo.

Sorry I missed this PR. Can you send it to https://github.com/react-navigation/react-navigation/tree/4.x/packages/native instead?

repo: react-navigation/native


text:
fix docs for InitialParams

It should be 'route.params.user' instead of route.params.me in the session The navigation prop ( https://reactnavigation.org/docs/upgrading-from-4.x/
Before:

Now:

Eu que agradeço @eriveltonelias


text:
feat: expose tab bar height

Motivation
Some user(s) mentioned their use case of wanting to implement a transparent tab bar. This is do-able by absolutely positioning the tab bar in tabBarOptions.style - However, when using this approach, it'd be ideal to have a way to access the tab bar height (e.g. to add padding if needed). This PR exposes the tab bar height as part of the public API via context.
Closes https://github.com/react-navigation/tabs/issues/184
Also somewhat related to https://github.com/react-navigation/tabs/issues/46
Test plan
A new example of a context aware transparent (absolutely positioned) tab bar was added to the example directory.

GIF of example

Updated the PR. Thanks for looking at this.

repo: react-navigation/tabs


text:
Find alternative of react-dnd and react-dnd-html5-backend

Checklist

[X] I've looked through the README
[X] I've verified that I'm running react-big-schedule version 4.2.0
[X] I've searched existing feature requests and confirmed that this request is not a duplicate

What problem does this feature solve?
This feature will help to find better solution for the core functionality of the library.
Proposed Solution
My first solution in mind is to implement our own drag and drop functionality.
Benefits
Better maintenance.
Alternatives Considered
No response
Additional Information
No response

As I mentioned above - my first solution in mind is to write our own dnd support code. But I will make research of the existing libraries.

As I mentioned above - my first solution in mind is to write our own dnd support code. But I will make research of the existing libraries.

Yeah good idea, I will also try to find any good alternative

Any progress here?

I tried to find it but still didn't get any proper library for same

@DamyanBG any progress still ?

No

authors: DamyanBG ansulagrawal whoafridi

repo: react-scheduler/react-big-schedule


text:
use-assets hooks

Hello! I report here what has already been done in the library that I have published in these days.
Since there is a new prototyping section, it makes sense to have assets-related hooks.
🛠 useNormalTexture (needs suspense)
Loads normal textures from this repository: https://github.com/emmelleppi/normal-maps
const [normalMap, url] = useNormalTexture(
  1, // index of the normal texture - https://github.com/emmelleppi/normal-maps/blob/master/normals.json
  // second argument is texture attributes
  {
    offset: [0, 0],
    repeat: [normRepeat, normRepeat],
    anisotropy: 8
  }
)

return (
  ...
  <meshStandardMaterial normalMap={normalMap} />
  ...
)

⚒ useMatcapTexture (needs suspense)
Loads matcap textures from this repository: https://github.com/emmelleppi/matcaps
(It is a fork of this repository: https://github.com/nidorx/matcaps)
const [matcap, url] = useMatcapTexture(
 0, // index of the matcap texture https://github.com/emmelleppi/matcaps/blob/master/matcap-list.json
 1024 // size of the texture ( 64, 128, 256, 512, 1024 )
)

return (
 ...
 <meshMatcapMaterial matcap={matcap} />
 ...
)

👉 You can also use the exact name of the matcap texture, like so:
const [matcap] = useMatcapTexture("3E2335_D36A1B_8E4A2E_2842A5");

👉 Use the url to download the texture when you are ready for production!
Last thing: right now the hooks fetch the data from my repos. It would make sense that those repos would be forked by react-spring, once done we can change the url with the new ones ✌🏼

great! whats still missing is referencing them in index.tsx and the github docs

ok, it should be fine 👍

authors: drcmda emmelleppi

repo: react-spring/drei


text:
Delay channel join until after AUTH NickServ on freenode

Not sure this is a bug, but an annoyance.  Freenode's NickServ takes some time to +r the bot, so much so that the bot is not authenticated until after it tries to join the channel.  Is there a way to sleep or wait for NOTICE to come back before channel joining or is there a way to retry channel join after a period of time.  I don't see anything in the code for this.  I've been manually inviting the bot to the channel in the meantime.

I think this is a duplicate of https://github.com/reactiflux/discord-irc/issues/426#issuecomment-410160092 and there is also your solution.

Thanks, I'll switch it.

authors: Mikaela wstearns

repo: reactiflux/discord-irc


text:
'ReactDOM' is not defined  no-undef  problem occurs while running this script?

code i used :
import ReactDOM from 'react-dom';
import React from 'react';
const App= () =>(

Hello first React project

)
ReactDOM.render(,document.getElementById('root'))
error i got :
Failed to compile.
src/index.js
Line 14:1:  'ReactDOM' is not defined  no-undef
Search for the keywords to learn more about each error.

can any one help me to solve this problem and say why it occurs because i beginner to this reactjs

You just have have to correct "import ReacrDOM from ...." into "import ReactDOM from react-dom"
The letter 'r' has to be replaced by 't' and give you and also, my advise will be to always put "import React from ...." on top
import ReactDOM from 'react-dom';
import React from 'react';

Make sure to close the issue and it would be great to leave me a star on my profile.
You can also fork this Todo-list and get a full ReactJS template project.
I am a ReactJS developer and will gladly help you if you have further questions or require an advice on this topic.
👍🏾
Eskabore

import React from "react";
import  ReactDOM from "react-dom";
import Heading from "./Heading";
import Para from "./Para";
import List from "./List"
function App(){
return (
<>

</>
);
}
export default App;

src\index.js
Line 4:1:  'ReactDom' is not defined  no-undef
Line 6:2:  'App' is not defined       react/jsx-no-undef
Search for the keywords to learn more about each error.

ReactDOM and ReactDom are different words, check your spelling ,it should be ReactDOM. React is case sensitive

Thank you for the response, I experienced the same problem then capitalized DOM then everything worked.

This is my code:
import ReactDOM from 'react-dom';
import React from 'react';
const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
<>

</>
)
and this is the error I'm getting:
[eslint]
src\root.js
Line 1:21:  'ReactDOM' is not defined  no-undef
Search for the keywords to learn more about each error.
ERROR in [eslint]

authors: Bobby-GMS Eskabore Nishikantaparhi ThulaMabota bravol naveen2103


text:
Tradução das páginas page 404 and editor-setup

Tradução para português brasileiro das páginas:

page 404
editor-setup

issue #555
Li a discussão da issue, o guia de contribuições, e o arquivo GLOSSARY.md onde encontrei o "Guia de Estilo Universal".

@vyamashiro consegue atualizar seu PR com a branch main, e tratar os conflitos, ae na sequência consigo revisar/aprovar

Vou fechar porque ambas as paginas já foram traduzidas, obrigado pela contribuição!

authors: jhonmike vyamashiro


text:
Responsive? HAHAHA

How does this package have this many stars? Every time you resize or change data, the fucking chart balloons up in size. Setting max-height doesn't work, wrapping in div doesn't work, EVERYTHING comes with a caveat such as labels taking up the majority of the size instead, etc.
Worthless. Piece. Of. Shit.

@cyllu2 Can you share the screenshots / video ?

People do open source for the good of their hearts. If you think a library is a piece of ****, keep that to yourself and write a better one. Or better yet, fix the issue. It's issues like this that make people leave open source.

It's issues like this that make people leave open source.

Good.

PRs accepted

authors: austinpray cyllu2 jorilallo khalednobani

repo: reactjs/react-chartjs


text:
Use callback ref instead of string

Not sure if you care about this, but I was browsing the source code and noticed you were still using a string ref. I just updated it to a callback ref.

Good call. I know some people may be relying on exact ref name in their test cases so I’ll probably hold this off until the next major.

Superseded by #416. (Sorry, JD!)

lol @timdorr, no worries :)

authors: gaearon jisaacks timdorr

repo: reactjs/react-redux


text:
Weird state binding bug

Hey guys, this is my first issue so please let me know if I am missing something.
So I am using functional components and using useState and SWR together.
I use a useEffect hook to watch for changes in dataOfFunnel and when there is a change, I set the state as the new data fetched.
but the problem is that when I change the state, dataOfFunnel is also affected as if they were bonded together.
here is a snippet of my code:
const {
        data: dataOfFunnel,
        dataLoading: initialFunnelLoading,
        isValidating: isInitialFunnelValidating
    } = getFromBackend<Funnel>(sharedConstants.routeToGetFunnelWithID, { funnelID: funnelId });
const [triggerSystem, setTriggerSystem] = useStateAsReducer<TriggerSystem>(null);

useEffect(() => {
                setTriggerSystem((previousTriggerSystem) => {
                    return { ...dataOfFunnel.result.triggerSystem}
                });
    }, [dataOfFunnel]);

Seems like I found an answer to my question.
Doing this seemed to fix my issue:
setTriggerSystem(JSON.parse(JSON.stringify(dataOfFunnel.result.triggerSystem)))

but I would have loved this to be enough:
setTriggerSystem({...dataOfFunnel.result.triggerSystem})

Thanks so much

Thanks so much

were you also having this issue?

This repository is for the React's website (https://reactjs.org). For React issues, please go to https://github.com/facebook/react/issues

@gaearon I think we can close this issue now.

authors: Crunchyman-ralph dev-tom-0108 shamwela


text:
react v 16 documentation is missing

no links for any prior React versions documentation is working

Yeah, this is a problem. We're tracking this in https://github.com/reactjs/reactjs.org/issues/3927.

Actually that's not where that issue is. Where is it?...

https://github.com/reactjs/reactjs.org/issues/4306 is the right issue.

authors: badbabykosh gaearon


text:
malayalam lang

This is a new PR created as per the comment on the previous pr. Malayalam is a regional language in Kerala, India.

I'm interested in joining forces. Can you add me as a maintainer @adarshm07 ?

Sounds good, creating the repo now.

Thank @gaearon

authors: adarshm07 asimkt gaearon


text:
🛑 Web Kartu Ujian is down

In e3ab77a, Web Kartu Ujian (https://kartuujian.sman12-bekasi.sch.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Web Kartu Ujian is back up in 0e75cbc after 6 minutes.


text:
don't send nil (null) to form components as the value string

This upsets react and produces warning messages.
Instead translate nil to "" on input.   If you want an uncontrolled component you can leave off the "value" field, or shovel undefined through.

@zetachang verify closed please

repo: reactrb/reactrb


text:
CSS-related issues in fixed-layouts

We’ve started working on the fixed-layout implementation.
While we won’t inject styles in there, authors and beta-testers might still report CSS-related issues I’ll then try to investigate.
Authors are also encouraged to report rendering issues they have encountered in Readium or any other Reading System so that we can check if it’s browser-related, markup-related, scaling-related, type-related, etc.

Might re-open if needed.

repo: readium/readium-css