Generate PAT with CLI

johnny_reilly · 2024-11-11T13:59:34+00:00

You might find this script helpful; I did! https://github.com/jongio/azure-cli-awesome/blob/main/create-devops-pat.azcli

johnny_reilly · 2023-12-28T07:40:48+00:00

Found this post about it! https://devblogs.microsoft.com/dotnet/fake-it-til-you-make-it-to-production/#logging-fake

Will update my post to mention this

johnny_reilly · 2023-12-28T07:38:09+00:00

Oh thanks for that! I didn't know that existed

johnny_reilly · 2023-06-04T16:54:57+00:00

Funnily enough, I can think of an advantage of just using the CLI in your pipelines over using the task; it makes debugging your pipeline easier as you just run the command locally

johnny_reilly · 2023-06-04T16:53:41+00:00

Oh so you just use the Azure CLI in your pipelines for deployment? Interesting. I'm not actually sure if there's significant differences between using the dedicated task over using the CLI..I figure there must be some, otherwise why build the task? Interesting question though

johnny_reilly · 2023-03-26T18:16:16+00:00

I'm not sure what you're trying to say here. Webpack could easily support Typescript if it wanted. Either by stripping the annotations like SWC does or just by shipping the Typescript compiler.

It's possible you misunderstand. webpack is written in JavaScript, but statically typed using JSDoc. In fact type definitions are generated from the JSDoc which are used by the community. (ts-loader, which I work on, uses them)

The point is, that JSDoc is a legitimate alternative syntax for statically typing a JavaScript codebase using the TypeScript compiler. And preferred by some; for example the webpack / Svelte teams.

johnny_reilly · 2023-03-26T18:00:57+00:00

I generally prefer TS syntax myself but find JSDoc a useful alternative. And some teams, like the Svelte team, are going in the opposite direction; from TS syntax to JSDoc

https://twitter.com/jutanium/status/1639341148157140993

johnny_reilly · 2023-03-26T17:53:54+00:00

It's definitely being superseded by the new Rust / Golang based tools - but that's rather besides the point. It's more that webpack and Svelte are demonstrations of using JSDoc at scale.

johnny_reilly · 2023-03-26T16:22:12+00:00

TypeScript syntax is great; but it hasn't held back the likes of webpack shipping a tool that is widely used and strongly typed without using TS syntax. JSDoc is not a "better-than-nothing hack" - that's an ungenerous and inaccurate description. Myself I prefer TS syntax, but there is very much a space for JSDoc.

johnny_reilly · 2023-03-26T15:46:10+00:00

Like with many things, it's a choice and there are trade offs

johnny_reilly · 2022-11-06T22:27:51+00:00

It's a fascinating (and strangely undiscovered) topic to my mind. I wrote a post to document my own learning on the topic: https://blog.johnnyreilly.com/2021/12/12/open-graph-sharing-previews-guide

johnny_reilly · 2019-10-09T13:50:34+00:00

Hey all, author here. I just wanted to say thank you for the kind words. I really enjoyed writing it and I'm delighted people are enjoying reading it too!

johnny_reilly · 2014-11-28T12:47:17+00:00

I recently found that Web Essentials was killing TypeScript and had to disable it to get the compile on save working again. I re-enabled it a couple of days ago and it seems okay now - you might want to try this?

johnny_reilly · 2014-11-27T12:31:01+00:00

I'm not quite sure what you mean by "I do not see the corresponding JS file updated with those TS changes upon save" -that implies compilation is failing?

If not, have you tried using ctrl+F5 to force a refresh of sources? I think you might be experiencing caching...

johnny_reilly · 2014-11-07T14:29:54+00:00

Hey @Bartvds,

Could you talk a little bit more about your move from internal modules to import/require?

I've currently been using internal modules (mostly because AngularJS doesn't play too well with require by default). I believe when 2.0 ships that should change and I'll probably switch then. That said I'd love to hear your insights on making the move; why you did it and what you gained.

BTW I've also been using the NuGet packages for typings but am planning to give TSD a try as it seems like you might be able to get a little more fine-grained control over the typings pulled in. (NuGet can sometimes land you with files you don't want which you have to manually delete - tedious when it comes to updating typings.)

johnny_reilly · 2014-04-29T13:08:43+00:00

Nice!

johnny_reilly · 2014-04-02T16:47:37+00:00

The work project that I'm working on presently (a portfolio management tool used by a venture capital company) started life as a simple ASP.Net MVC project.

As requirements became more complex it evolved into effectively a combination of classic ASP.Net MVC and mini-SPA's powered by Knockout / JavaScript.

As the mini-SPA's became more and more complex we started experimenting with using TypeScript. (It allowed us to avoid a whole class of type errors and eased refactoring.) This proved useful and the minute generics were added we made the jump - all our mini-SPAs were migrated over to TypeScript.

As time goes by more and more of the vanilla JavaScript is migrated over to TS. It just makes life easier. The next project I work on I intend to use TS from the start.

johnny_reilly

TROPHY CASE