profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/EduardoAraujoB/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Eduardo de Araújo Barreto EduardoAraujoB @letrustech Brazil Frontend Developer

lucasmontano/twitch 117

[EBS] Channel's Top Visitors

EduardoAraujoB/myapi 3

my first node api with express and MongoDB

EduardoAraujoB/typeorm-node 2

An API in Express using TypeORM

EduardoAraujoB/.vimrc 1

My vim configs

EduardoAraujoB/moovies-catalog-backend 1

An api with Typescript using Express, Sequelize and Jest

EduardoAraujoB/book 0

The Rust Programming Language

EduardoAraujoB/gobarber-backend 0

Rocketseat Bootcamp - GoBarber project

EduardoAraujoB/gobarber-mobile 0

Mobile App of GoBaber project from Rocketseat Bootcamp

EduardoAraujoB/gobarber-web 0

Web Front-end of the Gobarber Project from Rocketseat Bootcamp

push eventEduardoAraujoB/.vimrc

Eduardo de Araújo Barreto

commit sha 6478a710f0f1c5c83775f40f73f95dea5925deba

fix auto formatting on save

view details

push time in 11 days

issue commentdracula/vim

Better Highlight with Neovim Treesitter

ok, I saw that the #255 solves the same issue that I have, I have been using it for some weeks and the other problems that I saw is not related to the colorscheme itself (I guess), so the treesitter support is good as well, @benknoble if for some reason you change your mind and want to try neovim, I can help, as far as I can tell it is a way better than vim in lsp, color schemes, etc...

EduardoAraujoB

comment created time in 13 days

issue commentdracula/vim

Better Highlight with Neovim Treesitter

thanks a lot for your answer @adriantrunzo , it's working quite well, some of the problems that I had I figured out that it's related to treesitter itself and not the color scheme, but, I guess that it's not the case for this one image maybe it's related to a parser issue, but I tested it with tokyonight.nvim and got this image

EduardoAraujoB

comment created time in 13 days

issue commentdracula/vim

Better Highlight with Neovim Treesitter

@adriantrunzo you can use how vscode set the colors groups as a mental model and of course that there is differences between both of them, but the mainly goal is to define the color groups for values (which is usually in #6272a4), the color groups for functions (usually #50fa7b), reserved keywords (#ff79c6), function parameters (#ffb86c), comments (#6272a4).

also the full color palette is here https://draculatheme.com/contribute

EduardoAraujoB

comment created time in 18 days

push eventEduardoAraujoB/.vimrc

Eduardo de Araújo Barreto

commit sha 7beba0b6057f927ea6e96c67d80d4e3b959e1469

faster autolinting and autocomplete

view details

push time in 20 days

startedvrmiguel/bustd

started time in 21 days

issue commentdracula/vim

Better Highlight with Neovim Treesitter

I'm not sure about when and how treesitter will be included in neovim by default, but about the edge cases, some of them I figured out that it's related to parsing issues, anyway, if it doesn't make sense for the project right now, feel free to close the issue and we can open a new one when treesitter gets more stable

EduardoAraujoB

comment created time in a month

push eventEduardoAraujoB/.vimrc

Eduardo de Araújo Barreto

commit sha 49f635ff25ebda24f9d6805d29f5c38f3cc06d63

blow up coc.nvim and switch to bultin lsp >:)

view details

push time in a month

startedRust-for-Linux/linux

started time in a month

issue commentdracula/vim

Better Highlight with Neovim Treesitter

neovim 0.5 released today, I told that it was soon 🙂

EduardoAraujoB

comment created time in a month

startedmhartington/formatter.nvim

started time in a month

issue commentimmutable-js/immutable-js

Better Type Inference

@jdeniau so, there is a problem on your implementation, as I said, it will not work for deep nested objects, for and example, if for some reason you have

const user = { name: 'name', profile: { role: 'user' } };

and a interface like this

interface User {
  name: string;
  profile: { role: string };
}

so what will happens when you put it into a fromJS? it will deep convert all your objects into a Map and arrays as List, but the problem is that it will not infer the role is a Map also, so the we will need to change all their interfaces hardcoding types because it's not inferred properly (or keeping everything as any), and there is a huge problem if was not us that made that interface, we will need to override the types of other libraries or re-create it by hand which is bad, that's why I'm using that ImmutableMap type to infer everything properly and it's working good so far

EduardoAraujoB

comment created time in a month

issue commentimmutable-js/immutable-js

Better Type Inference

yeah, this solution worked well and fixed my problems for type inference, but there is problems in this implementation, the first one is that the getIn type inference only works with a maximum of 4 properties and to make it work for more we need to keep repeating getIn function with more arguments, other problem is that this implementation doesn't implement the types for all the functions that Map provides, and the last one is more complicated, sometimes it's hard to know if something is in a Immutable way or not, for an example, Records doesn't apply deep conversion, so the first object is in a Immutable way and the second one isn't, but when we use the fromJS it does, so know when something is immutable or not is complicated

EduardoAraujoB

comment created time in a month

issue commentreact-cropper/react-cropper

Right Types For Refs

worked, thanks a lot

EduardoAraujoB

comment created time in a month

startedhecrj/iced

started time in a month

issue commenttree-sitter/tree-sitter-typescript

Wrong Highlight When a Union Type Inside a Generic Starts With null

thanks for reproducing the problem, I'm still a newbie on vim/nvim so I have no idea about how treesitter works and how to write a solution for that

EduardoAraujoB

comment created time in a month

issue commentreact-cropper/react-cropper

Right Types For Refs

@shekhar-shubhendu thanks, I will be waiting the release to replace the local types that I made as a workaround for this problem

EduardoAraujoB

comment created time in a month

issue openedtree-sitter/tree-sitter-typescript

Wrong Highlight When a Union Type Inside a Generic Starts With null

Problem

so I've found this bug in the highlighting image as you can see, if I start the generic with a null then this error happens, a good question also is if null should be highlighted as a reserved keyword, as a type, or as a value (types are highlighted in my color scheme, values are purple and reserved keywords are pink)

created time in a month

issue openedreact-cropper/react-cropper

Right Types For Refs

Problem

Currently the documentation recommends to set the cropper ref types as HTMLImageElement, then the user try to use the getCroppedCanvas function from the ref and got a type error saying that HTMLImageElement doesn't have the getCroppedCanvas function (and it doesn't), so your types are wrong and it's forcing the users to type their constants as any which is bad

Solution

so if the types of the reference is a modified version of the HTMLInputElement the solution is simple, extend that input and then add the definitions and overrides that the cropper is doing over it (which is what I'm doing locally in my project to fix it)

created time in a month

startedVitorVilela7/wide-snes

started time in a month

pull request commentmelange-re/melange

Support Unicode Directories

anyway, I'm still having problems to know what is the correct way for dune to recognize that paths

EduardoAraujoB

comment created time in 2 months

pull request commentmelange-re/melange

Support Unicode Directories

So, here is the problem, by using the Format.asprintf "%S" on the Ext_filename.maybe_quote_for_dune OCaml will ecape it to something like this src/\206\179\206\189\207\137\207\129\206\175\206\182\207\137, but using the Format.asprintf {| "%s" |} it will generate this src/γνωρίζω (which is the unicode name of the folder)

EduardoAraujoB

comment created time in 2 months

pull request commentmelange-re/melange

Support Unicode Directories

@anmonteiro there is a problem with the maybe_quote_for_dune helper, it's not escaping properly the unicode characters

(progn (dynamic-run bsb_helper -root /home/eduardo/Downloads/ocaml-reason/melange-basic-template -cwd "./src/\206\179\206\189\207\137\207\129\206\175\206\182\207\137" %{ast_deps}) (run bsc -I . -I ..    -w a -bs-package-name melange-basic-project -bs-package-output commonjs:"./src/\206\179\206\189\207\137\207\129\206\175\206\182\207\137":.bs.js -o tuturuu.cmj %{inputs})))

as you can see, it's escaping the unicode directories to numbers, instead of just the unicode text quoted

EduardoAraujoB

comment created time in 2 months

pull request commentmelange-re/melange

Support Unicode Directories

thanks, didn't knew about the Ext_filename.maybe_quote_for_dune, will apply the fixes asap

EduardoAraujoB

comment created time in 2 months

push eventEduardoAraujoB/melange

eduardoaraujob

commit sha 6691351a9dec4009ffde4599bbb5ca99411aa243

add TODO for commented code on Ext_string

view details

eduardoaraujob

commit sha 2effafe3d00f6148a263af7825d7b775710836a9

quoting parameter passed to -bs-package-output

view details

push time in 2 months

issue commentmelange-re/melange

Quote directories passed to dune

@anmonteiro I found a problem on the implementation of this issue, so on the generated dune file there is a (progn which contains the -bs-package-output with commonjs:./src/subfolders:.bs.js so the problem is without quoting the parameter passed to -bs-package-output the dune file will return errors with unicode directories (as the comment above), but if I quote this to something like this "commonjs:./src/subfolders:.bs.js" then this problem will happens

image

I will update the PR with this changes

anmonteiro

comment created time in 2 months

issue commentdracula/vim

Better Highlight with Neovim Treesitter

@dsifford Neovim nightly is planned to release soon, but if it doesn't make sense for the project by now, I can just close the issue

EduardoAraujoB

comment created time in 2 months

issue commentdracula/vim

Better Highlight with Neovim Treesitter

@benknoble treesitter comes with new highlight groups which vim doesn't recognize, the problem that I'm having is to make dracula nvim work properly with this new groups on TSX/JSX, currently it doesn't show different higlights for variables, functions and JSX props, when the highlight is enabled by doing this lua require'nvim-treesitter.configs'.setup { highlight = { enable = true } } on my init.vim, it changes the way that nvim handles highlight groups, enabling that blue color for type definitions, but for some reason it doesn't work properly on the other cases that I showed, because the colorscheme doesn't give full support for nvim treesitter

EduardoAraujoB

comment created time in 2 months

issue openeddracula/vim

Better Highlight with Neovim Treesitter

Problem

Neovim 0.5 comes with treesitter, a plugin that improves a lot the syntax highlighting as described in the (repository)[https://github.com/nvim-treesitter/nvim-treesitter], but by using it with higlight enabled, I got weird higlights for some groups in TSX/JSX (in JS/TS files it works fine)

What happened

image image

What I expected to happen

on my vscode, I got this image image

Screenshot

Machine Info

<!-- if on a *nix system, please provide the output of uname -a for OS field -->

  • NVIM v0.5.0-dev:
  • OS: Ubuntu 20.04:
  • Terminal: Tilix with Tmux:
  • TERM: xterm-256color:

Additional Info

my neovim configs

created time in 2 months

push eventEduardoAraujoB/.vimrc

Eduardo de Araújo Barreto

commit sha 101d71286ebcd79524f00d979766b19f7b39898c

update neovim configs

view details

push time in 2 months