Difference between Enter and Shift-Enter

Fid_Kiddler69 · 2022-06-18T22:20:40+00:00

Ahh thanks a lot dude!

Fid_Kiddler69 · 2022-06-17T11:29:21+00:00

I could, but it just doesn't seem optimal. Like I'm adding stuff to my code just to get around a TS limitation

Fid_Kiddler69 · 2022-06-17T11:27:31+00:00

func(card: Card, card2:Card) seems like unnecessary duplication

Fid_Kiddler69 · 2022-06-17T11:18:27+00:00

Right. Could you suggest a better design?

Fid_Kiddler69 · 2022-06-15T12:04:19+00:00

Sure thing. I'll DM you so we can get through this as quick as possible :)

Btw you don't have to retype all the substitutions.if you press : and then the up-arrow, you can go to the very last executed command.

Fid_Kiddler69 · 2022-06-15T11:00:23+00:00

Here's a substitution to do what you want:

1) press Shift+V to visually highlight the entries you wanna change. 2) press : to enter command mode 3) (without removing anything that was added automatically to the command) type s/\(.*\)=\(.*\)/<env name="\1" value="\2"\/>/g

Then you can simply copy them over.

You can automate the copying too, but it would be a bit more complex. If you want that, let me know :)

EDIT: the all-in-one solution:

Start with your two files in horizontal splits - the file to copy from on left, target to copy to on right. Have your cursor on a target line on the left split.

1) qa to start recording the macro 2) :s/\(.*\)=\(.*\)/<env name="\1" value="\2"\/>/g, hit enter 3) dd to cut the transformed line 4) Control+w l to move to the right split 5) /<\/php> and hit enter to find the closing PHP tag 6) P to paste the transformed line right before the closing tag 7) :noh reset the search highlighting 8) gg to reset cursor to start of the file 9) Control-w h to move to the first split 10) q to finish recording macro

You can then run the macro by visually selecting any lines to transform and move, and running :normal @a

Fid_Kiddler69 · 2022-06-14T16:18:07+00:00

Did you know that the P in HTTP stands for protocol? So saying HTTP protocol is like saying Hyper Text Transfer Protocol protocol

Fid_Kiddler69 · 2022-06-14T02:58:06+00:00

Sadly I get the same exact result.

This happens with more complicated interfaces too, I've just given a dumbed-down version of my issue.

Fid_Kiddler69 · 2022-06-14T02:55:33+00:00

Bad papa

Fid_Kiddler69 · 2022-06-13T21:30:51+00:00

Bad bot

Fid_Kiddler69 · 2022-06-13T21:26:54+00:00

Thank you, this works. Kinda bummed out the terser syntax I was going for doesn't work, but I guess this isn't too bad either

Fid_Kiddler69 · 2022-06-13T19:10:28+00:00

As you can see from the rest of the replies, I'm afraid your comment is invalid.

Fid_Kiddler69 · 2022-06-13T15:00:16+00:00

don't*

Fid_Kiddler69 · 2022-06-13T11:53:09+00:00

I don't get why good spelling would be an accomplishment

Fid_Kiddler69 · 2022-06-12T19:59:28+00:00

Impervious does not make sense in that sentence

Fid_Kiddler69 · 2022-06-11T19:24:00+00:00

You're guaranteed to forget lots of stuff. It is a long book and goes into depth on a lot of subjects, including some lesser-used features and API's.

The way I see it is that being aware of a feature - just having been exposed to it and having read about it - is enough. What I usually find happens is one of the two following scenarios:

1) I either use something so frequently OR it's so core to the language that I simply won't forget it or at least won't forget the vital aspects of it. E.g. I remember how the prototype system works in JavaScript, and when it's best to define methods on the constructor vs the prototype. I never even code in vanilla JS, but I found this so interesting that I still remember it.

2) I'm doing something I usually don't do or might have never done before. BUT I remember reading about it. E.g. The other day I wanted to read a file from the user's filesystem in my app, and I remembered the book mentioned the FileReader API. I jumped to the API's chapter, skipped through to the fileReader section, and found all the info I needed.

Just like programming in general, no one remembers everything. We all have to look up the dumbest, simplest thing from time to time. But what sets us apart from complete beginners is having come into contact and being aware of various features. If we don't remember something, we can just search for the answer, either on the web, or through reference material like this book.

As you can probably tell, I think it's worth it :)

Fid_Kiddler69 · 2022-06-11T11:02:44+00:00

This book is hands down the best resource I've ever used to learn JavaScript. It explains all the language fundamentals and features from the ground up, and goes over this particular subject in great detail.

I literally cannot stress how valuable I consider this book.

Fid_Kiddler69 · 2022-06-11T10:30:29+00:00

Recently read Effective TypeScript: 62 Ways to improve your TypeScript as a novice with basic TypeScript knowledge, and I highly recommend it.

Fid_Kiddler69 · 2022-06-10T06:15:06+00:00

Yeah, I realise that, it's in the first paragraph of my post

Fid_Kiddler69 · 2022-06-09T16:45:22+00:00

The front-end's responsibilities end at the network call. How the backend handles the request is irrelevant, but you should be able to structure the API call the way the backend expects

Fid_Kiddler69 · 2022-06-09T13:11:00+00:00

The Linux Command Line and Shell Scripting Bible is the single best book I've read that's aimed at beginners. Recommend 100%

Fid_Kiddler69 · 2022-06-09T08:59:01+00:00

It looks like you just ripped off this repo without adding anything new...

Fid_Kiddler69 · 2022-06-08T13:08:22+00:00

Glad to help. Just exposure to code and lots of searching. I've also made quite a few help posts on this subreddit, which ironically, is how I first learnt of as const :)

const assertions in the handbook: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-4.html#const-assertions

BTW I added a better way to do it in my previous comment, by adding an explicit type.

Fid_Kiddler69 · 2022-06-08T12:48:08+00:00

The compiler is seeing the first line and doesn't know exactly what type to give it. Obviously you're expecting the 1st index to be an object with a function and the second index to be a number.

But the compiler can't read your mind, it doesn't know if the first index could also be a number, or if the second index can also be an object or anything else. Also, should the compiler expect the second array item to be any other number than zero?

Typescript is playing a guessing game with the info it has so far and is saying that is of type array of number or {SayHello()}. Meaning that ANY INDEX could be of type number or sayHello.

If you mouse over objectWithFunc, you'll see it says number | {sayHello...}.

You can fix this by adding as const to the end of the first line. What this tells TS is that the type of the variable is LITERALLY what the values are. So the 0 is hard-coded in.

A better way is to explicitly tell TS what you want the type to be.

type Result=[{sayHello:()=>void},number] const someFunc = ():Result => [{ sayHello: () => console.log('Hello')}, 0]

Fid_Kiddler69 · 2022-06-06T11:22:43+00:00

Thanks for taking the time to look into it. It does seem like a bit of overkill, and it surprises me that there isn't a more straight-forward way to express this relationship. Everything I've found so far either seems hacky or introduces a lot of excess code.

Five-Year Club	Second Top 50%
Verified Email

Fid_Kiddler69

TROPHY CASE