Skip to content

Conversation

@vladfrangu
Copy link
Member

@vladfrangu vladfrangu commented Oct 23, 2024

create cmds
Code - 2024-10-23 at 12 30 27@2x

rm cmds (ignore the missing space, it has been fixed after taking the screenshot)
Code - 2024-10-23 at 12 43 17@2x

rename cmds
Code - 2024-10-23 at 13 13 05@2x

@vladfrangu vladfrangu added the adhoc Ad-hoc unplanned task added during the sprint. label Oct 23, 2024
@vladfrangu vladfrangu requested a review from B4nan October 23, 2024 09:30
@github-actions github-actions bot added this to the 101st sprint - Tooling team milestone Oct 23, 2024
@github-actions github-actions bot added the t-tooling Issues with this label are in the ownership of the tooling team. label Oct 23, 2024
@vladfrangu vladfrangu changed the title feat: datasets create / key-value-stores create feat: datasets create / key-value-stores create & rm counterparts Oct 23, 2024
@vladfrangu vladfrangu changed the title feat: datasets create / key-value-stores create & rm counterparts feat: datasets / key-value-stores commands Oct 23, 2024
@vladfrangu vladfrangu force-pushed the feat/storage-creates branch 2 times, most recently from 3761d5e to db1473c Compare October 23, 2024 10:18
@vladfrangu vladfrangu enabled auto-merge (rebase) October 23, 2024 10:18
Copy link
Member

@B4nan B4nan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looking good, but derails from the specs in the create --name i believe

static override description = 'Creates a new Dataset on your account';

static override args = {
datasetName: Args.string({
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not call this just name? we are in the datasets namespace, so it should be clear, no?

looking at the specs, there actually is just --name instead of --dataset-name. or this is positianal argument? again, specs mentions --name instead

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to poke @netmilk about this. We've had some other commands before that took --name as a flag that was then changed to a positional argument.

})();

try {
await existingDataset.datasetClient.update({ name: unname ? (null as never) : newName! });
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds like the types in client should be updated to allow null

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah... among many other type changes that the client needs to get 😢. I'm really hoping we can stop manually maintaining these types and build from openAPI but even that spec misses fields -w-

static override hiddenAliases = ['kvs:create'];

static override args = {
keyValueStoreName: Args.string({
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, specs say it should be a --name flag

(no strong opinion here, i don't mind either)

@vladfrangu vladfrangu disabled auto-merge October 30, 2024 16:38
B4nan added a commit to apify/apify-client-js that referenced this pull request Nov 1, 2024
janbuchar pushed a commit to apify/apify-client-js that referenced this pull request Nov 1, 2024
@vladfrangu vladfrangu enabled auto-merge (squash) November 18, 2024 07:37
@vladfrangu vladfrangu merged commit c7d77e1 into master Nov 18, 2024
17 checks passed
@vladfrangu vladfrangu deleted the feat/storage-creates branch November 18, 2024 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants