orta

orta

I help people build dev ecosystems. Current: TypeScript. Contributed to: Shiki, Shiki Twoslash, Danger, CocoaPods, Jest, GraphQL, RxSwift & Svelte.

Member Since 12 years ago

Microsoft on TypeScript, Huddersfield / NYC / Dublin

Experience Points
4.9k
follower
Lessons Completed
104
follow
Lessons Completed
389
stars
Best Reply Awards
891
repos

4225 contributions in the last year

Pinned
⚡ ⚠️ Stop saying "you forgot to …" in code review
⚡ TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
⚡ The Cocoa Dependency Manager.
⚡ The Art World in Your Pocket or Your Trendy Tech Company's Tote, Artsy's mobile app.
Activity
Oct
24
13 hours ago
Activity icon
issue

orta issue comment tsconfig/bases

orta
orta
orta
orta

I've fixed CI and shipped this- thanks

push

orta push tsconfig/bases

orta
orta
orta
orta

Add Vite React to README

orta
orta

Merge pull request #77 from tsconfig/hnordt-main

Vite TS Config

commit sha: 8d8e9131990a0d3716a2da3807627805d4127db4

push time in 1 hour ago
pull request

orta pull request tsconfig/bases

orta
orta

Vite TS Config

I couldn't edit #73

pull request

orta pull request tsconfig/bases

orta
orta

Vite TS Config

I couldn't edit #73

Activity icon
created branch

orta in tsconfig/bases create branch hnordt-main

createdAt 2 hours ago
Oct
23
1 day ago
push

orta push microsoft/TypeScript-Website

orta
orta

Adds support for showing queries using inlay hints if it is available

orta
orta
orta
orta

Merge pull request #2105 from orta/inlays

Adds support for showing queries using inlay hints if it is available

commit sha: 28ea606ab693a140612d9fa6b9bbd1c66f361449

push time in 16 hours ago
pull request

orta pull request microsoft/TypeScript-Website

orta
orta

Adds support for showing queries using inlay hints if it is available

Adds twoslash query results as inline highlights

pull request

orta pull request microsoft/TypeScript-Website

orta
orta

Adds support for showing queries using inlay hints if it is available

Adds twoslash query results as inline highlights

Activity icon
created branch

orta in orta/TypeScript-Website create branch inlays

createdAt 17 hours ago
Oct
22
2 days ago
Activity icon
issue

orta issue comment type-challenges/type-challenges

orta
orta

IsPalindrome

Please follow the template and fill the info. A PR will be auto-generated and always reflect on your changes.

Detailed solution/guide is not required, but please be sure the challenge is solvable.

Info

Basic info of your challenge questions,

difficulty: hard
title: IsPalindrome
tags: string

Question

Implement type IsPalindrome<T> to check whether a string or number is palindrome.

For example:

IsPalindrome<'abc'> // false
IsPalindrome<121> // true

Template

This is the template for challengers to start the coding. Basically, you just need to change the name of your generic/function and leave to implementation any.

type IsPalindrome<T> = any

Test Cases

Provide some test cases for your challenge, you can use some utils from @type-challenges/utils for asserting.

import { Equal, Expect, ExpectFalse, NotEqual } from '@type-challenges/utils'

type cases = [
  Expect<Equal<IsPalindrome<'abc'>, false>>,
  Expect<Equal<IsPalindrome<'b'>, true>>,
  Expect<Equal<IsPalindrome<'abca'>, false>>,
  Expect<Equal<IsPalindrome<121>, true>>,
  Expect<Equal<IsPalindrome<19260817>, false>>,
]
orta
orta

haha, what a great idea

Activity icon
created repository
createdAt 2 days ago
Activity icon
issue

orta issue comment redwoodjs/redwood

orta
orta

Update README.md with testing details

Was just reading this, thought it needs a small update

orta
orta

Not a blocker, but storybook support could go in that section too

Activity icon
issue

orta issue comment danger/danger

orta
orta

Post comment to Bitbucket Server only if there is any content

This PR adds a simple check to see if a comment should be posted to Bitbucket Server.

The #1299, describes the issue pretty well, but in short, there are some implementation differences between Github and BBS.

Both platforms have the same concepts of comments and build statuses. On Github there are two actions, comment posting and setting build status. On BBS the build status update is not fully implemented, but there are methods already so it could be easily finished if needed. Though because BBS requires a build URL, it makes posting one from danger a bit awkward

Now I don't know if there were status badges when the original implementation was done, but now that there is the Code insights implementation, which adds its own status badge to the PR page, sending a separate build status update might be unnecessary.

Activity icon
published release 8.4.1

orta in danger/danger create published release 8.4.1

createdAt 2 days ago
Activity icon
created tag

orta in danger/danger create tag 8.4.1

createdAt 2 days ago
Activity icon
created tag

orta in danger/danger create tag v8.4.1

createdAt 2 days ago
push

orta push danger/danger

orta
orta

Post comment to BBS only if there is any content

orta
orta

Merge pull request #1331 from pahnev/master

Post comment to Bitbucket Server only if there is any content

commit sha: b6b0673b9128ced099ea2e5cdfb533b4cad03c1d

push time in 2 days ago
pull request

orta pull request danger/danger

orta
orta

Post comment to Bitbucket Server only if there is any content

This PR adds a simple check to see if a comment should be posted to Bitbucket Server.

The #1299, describes the issue pretty well, but in short, there are some implementation differences between Github and BBS.

Both platforms have the same concepts of comments and build statuses. On Github there are two actions, comment posting and setting build status. On BBS the build status update is not fully implemented, but there are methods already so it could be easily finished if needed. Though because BBS requires a build URL, it makes posting one from danger a bit awkward

Now I don't know if there were status badges when the original implementation was done, but now that there is the Code insights implementation, which adds its own status badge to the PR page, sending a separate build status update might be unnecessary.

Activity icon
issue

orta issue comment danger/danger

orta
orta

Post comment to Bitbucket Server only if there is any content

This PR adds a simple check to see if a comment should be posted to Bitbucket Server.

The #1299, describes the issue pretty well, but in short, there are some implementation differences between Github and BBS.

Both platforms have the same concepts of comments and build statuses. On Github there are two actions, comment posting and setting build status. On BBS the build status update is not fully implemented, but there are methods already so it could be easily finished if needed. Though because BBS requires a build URL, it makes posting one from danger a bit awkward

Now I don't know if there were status badges when the original implementation was done, but now that there is the Code insights implementation, which adds its own status badge to the PR page, sending a separate build status update might be unnecessary.

orta
orta

Yeah, this makes sense to me 👍🏻

Activity icon
issue

orta issue comment danger/danger-js

orta
orta

Upgrade http-proxy-agent and https-proxy-agent to fix #1155

#1155 describes a bug that arises when using gitbeaker with Danger. This PR includes the fix suggested in #1155 by @locomike.

Thanks @locomike!

orta
orta

Looks like there's a few changes that this will require in the codebase too 👍🏻

Oct
21
3 days ago
Activity icon
issue

orta issue comment microsoft/TypeScript

orta
orta

🤖 Sync option descriptions <- jablko/TypeScript-Website

Get command-line option descriptions from the website Markdown and update their corresponding descriptions in the compiler.

\cc @orta

orta
orta

you might have changed the line endings on the JSON file - the diff is basically the file

https://twitter.com/kclemson/status/1451238009664278528

push

orta push orta/TypeScript-Website

orta
orta

Apply suggestions from code review

Co-authored-by: Nathan Shively-Sanders [email protected]

commit sha: 2789ad5295d8d718697279bfa3dc972a938554ad

push time in 2 days ago
push

orta push microsoft/TypeScript-Website

orta
orta

Apply suggestions from code review

Co-authored-by: Nathan Shively-Sanders [email protected]

commit sha: 762e45f62656197a9a7e61f66671de9f13836bc3

push time in 2 days ago
push

orta push microsoft/TypeScript-Website

orta
orta

More work on the playgground handbook

commit sha: 57aee7c65b5360f2cf3ee7ccb3d74cc4d59e141e

push time in 2 days ago
Previous