profile
viewpoint
Andriy Semenets semanser Lutsk, Ukraine

semanser/dotfiles 42

Alacritty + Tmux + Oh My Zsh + Neovim = ❤️

semanser/vim-outdated-plugins 41

🔄 Async Vim/Neovim plugin for showing the number of your outdated plugins

VisualTranslator/VisualTranslator 5

[Under Development] 🔠 AI-based recognition and translation desktop tool

semanser/png-pixel 3

🖌️ Draw pixels in PNG easily

VisualTranslator/visualtranslator.github.io 1

Official website source code

semanser/awesome-tmux 0

A list of awesome resources for tmux

semanser/gina.vim 0

Asynchronously control git repositories in Neovim/Vim 8

semanser/graphiql 0

An in-browser IDE for exploring GraphQL.

startedpuremourning/vimspector

started time in 4 days

startedbkrem/react-d3-tree

started time in 16 days

starteduber/react-digraph

started time in 16 days

issue commentrecharts/recharts

Pie Chart - No Label Shown

It would be nice to have a repo where this bug can be reproduced. Or maybe jsfiddle.

quangas

comment created time in 25 days

startedwebpack-contrib/eslint-loader

started time in a month

startedartichoke/artichoke

started time in a month

issue commentapollographql/apollo-client

Components never get updated after `writeData` or `writeQuery`

Short answer: just use client.writeQuery instead of cache.writeQuery when you want your changes to be reflected in the UI immediately.

Long answer (from docs):

  1. The cache you created with new InMemoryCache(...) class is not meant to be used directly, but passed to the ApolloClient constructor. The client then accesses the cache using methods like readQuery and writeQuery. The difference between cache.writeQuery and client.writeQuery is that the client version also performs a broadcast after writing to the cache. This broadcast ensures your data is refreshed in the view layer after the client.writeQuery operation. If you only use cache.writeQuery, the changes may not be immediately reflected in the view layer. This behavior is sometimes useful in scenarios where you want to perform multiple cache writes without immediately updating the view layer.

  2. The update function receives cache rather than client as its first parameter. This cache is typically an instance of InMemoryCache, as supplied to the ApolloClient constructor whent the client was created. In case of the update function, when you call cache.writeQuery, the update internally calls broadcastQueries, so queries listening to the changes will update. However, this behavior of broadcasting changes after cache.writeQuery happens only with the update function. Anywhere else, cache.writeQuery would just write to the cache, and the changes would not be immediately broadcast to the view layer. To avoid this confusion, prefer client.writeQuery when writing to cache.

Source: https://github.com/apollographql/apollo-client/pull/4664/files

wzup

comment created time in a month

startedwez/wezterm

started time in a month

startedtssm/up-to-date-real-world-haskell

started time in a month

startedjunegunn/vim-peekaboo

started time in a month

startedliuchengxu/eleline.vim

started time in a month

startedneoclide/coc-smartf

started time in a month

startedgrain-team/vttyl

started time in a month

startedwellle/context.vim

started time in a month

startedseanmonstar/reqwest

started time in 2 months

pull request commentgraphql/graphiql

Add VIM keybindings support

@acao so, I guess adding more tests has no sense, because this PR is going to be rejected?

semanser

comment created time in 2 months

push eventsemanser/graphiql

Andriy Semenets

commit sha 51bdc0e7bb3aecfcb5b656f28f1676b760a694b5

Add even more tests

view details

push time in 2 months

pull request commentgraphql/graphiql

Add VIM keybindings support

ugh i hate to do this because you did a great job of implementing this, and i asked you to add tests. That's totally fine, don't worry :)

for your purposes currently, is there a way you can just require codemirror-vim in a way that overwrites those bindings in a more minimal fashion?

What do you mean with that? Right now, I'm using the default codemirror vim keybindings (and I guess they should work fine). I guess for now, this implementation can work pretty well, and can be replaced later with plugins.

semanser

comment created time in 2 months

push eventsemanser/graphiql

Andriy Semenets

commit sha f9571c198dd5b5c1ec758825fc6aacdefdcab438

Add more tests

view details

push time in 2 months

Pull request review commentgraphql/graphiql

Add VIM keybindings support

 export class QueryEditor extends React.Component {     require('codemirror/addon/dialog/dialog');     require('codemirror/addon/lint/lint');     require('codemirror/keymap/sublime');+    require('codemirror/keymap/vim');

For the toggling between vim/sublime modes, we need to have these files to be preloaded.

semanser

comment created time in 2 months

push eventsemanser/graphiql

Andriy Semenets

commit sha c66374fb8e8db24b3f4262e800fdeb14226f4dea

Add basic tests

view details

push time in 2 months

startedyarnpkg/yarn

started time in 2 months

startedhecrj/iced

started time in 2 months

issue commentrecharts/recharts

Pie Chart - No Label Shown

I was trying to investigate this issue, because I was getting it before, but it seems like all the demos are working fine right now.

Can someone reproduce this issue with the latest version of recharts and yarn demo command?

quangas

comment created time in 2 months

PR opened graphql/graphiql

Add VIM keybindings support

Issue: https://github.com/graphql/graphiql/issues/909

This PR brings VIM key bindings support to the Graphiql.

Features:

  • [x] Query editor
  • [x] Variables editor
  • [x] Toggle keybinding: Cmd-\ or Ctrl-\
  • [x] Local storage persistance
  • [x] Passing like an option to theGraphiQL component
+87 -24

0 comment

3 changed files

pr created time in 2 months

push eventsemanser/graphiql

Andriy Semenets

commit sha b8bb7c5fee3d5431c369561e296afaaca5e4f30b

Add keyMap support for the VariableEditor

view details

push time in 2 months

push eventsemanser/graphiql

Andriy Semenets

commit sha 3ab07be376ded524f9054fb2f481ffb49bbfbeca

Save keyMap to the local storage

view details

push time in 2 months

create barnchsemanser/graphiql

branch : add-vim-keybindings

created branch time in 2 months

fork semanser/graphiql

An in-browser IDE for exploring GraphQL.

fork in 2 months

startedgraphql/graphiql

started time in 2 months

startedpastelsky/bundlephobia

started time in 2 months

startedRasukarusan/fzf-chrome-active-tab

started time in 2 months

startedsindresorhus/query-string

started time in 2 months

startedjoshdick/dntw

started time in 2 months

pull request commentsemanser/vim-outdated-plugins

Use origin/branch when checking for new commits + python rewrite

It seems like I'm not able to add commits to this PR (I can't push to your branch).

thisisrandy

comment created time in 3 months

pull request commentsemanser/vim-outdated-plugins

Use origin/branch when checking for new commits + python rewrite

hi @thisisrandy! Thanks for your work and sorry for my late reply.

I've tried it and it works much better than vimscript version. Good job!

What is the minimal version of python required? I want to update the README file.

thisisrandy

comment created time in 3 months

starteditchyny/calendar.vim

started time in 3 months

startedreact-spring/react-spring

started time in 3 months

startedfaltimiras/GlacierBackupper

started time in 3 months

startedtypescript-cheatsheets/react-typescript-cheatsheet

started time in 3 months

startedLeaflet/Leaflet

started time in 3 months

startedsindresorhus/Gifski

started time in 3 months

startedwting/autojump

started time in 3 months

startedIMOKURI/line-number-interval.nvim

started time in 3 months

startedliuchengxu/vista.vim

started time in 4 months

startedappleboy/telegram-action

started time in 4 months

startedsmooth-code/loadable-components

started time in 4 months

more