Skip to content

Rename /client to /datajunction-clients.#670

Merged
agorajek merged 8 commits intomainfrom
issue-630
Jul 28, 2023
Merged

Rename /client to /datajunction-clients.#670
agorajek merged 8 commits intomainfrom
issue-630

Conversation

@agorajek
Copy link
Copy Markdown
Member

@agorajek agorajek commented Jul 27, 2023

Summary

Just the top level rename.

Test Plan

Also started docker compose --profile demo up and made sure the UI and Jupyter work.

  • PR has an associated issue: #
  • make check passes
  • make test shows 100% unit test coverage

Deployment Plan

n/a

@netlify
Copy link
Copy Markdown

netlify bot commented Jul 27, 2023

Deploy Preview for thriving-cassata-78ae72 canceled.

Name Link
🔨 Latest commit 2227344
🔍 Latest deploy log https://app.netlify.com/sites/thriving-cassata-78ae72/deploys/64c31b5e7fe59900085f4a94

@samredai
Copy link
Copy Markdown
Contributor

Shouldn't it be plural, i.e. "clients"?

@agorajek
Copy link
Copy Markdown
Member Author

@samredai good point.

@agorajek agorajek changed the title Rename client to datajunction-client. Rename /client to /datajunction-clients. Jul 27, 2023
@agorajek agorajek requested review from samredai and shangyian July 27, 2023 22:46
Copy link
Copy Markdown
Collaborator

@shangyian shangyian left a comment

Choose a reason for hiding this comment

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

LGTM! Only one minor comment on the path rename, but feel free to keep that change if you think it's more consistent.


@router.get(
"/client/python/add_materialization/{node_name}/{materialization_name}",
"/datajunction-clients/python/add_materialization/{node_name}/{materialization_name}",
Copy link
Copy Markdown
Collaborator

@shangyian shangyian Jul 27, 2023

Choose a reason for hiding this comment

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

To clarify, I don't think this route needs to change, I meant that the contents instead of (for example) client_code_for_adding_materialization will need to change, since we've updated the client code significantly, like the split between DJClient and DJBuilder. But that change can go into a different PR after we've stabilized the client methods

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@shangyian but then what is this reference to client/python/... ?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Ah, I guess I didn't think of it as a reference to the directory path, but yeah, interpreting it that way makes sense.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@agorajek this is just the REST API endpoint that the UI calls to return the example snippets it displays. I don't think it has anything to do with the directory path, it was just a coincidence that there was a /client/python/ directory and this REST endpoint was GET /client/python/....

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Ah I see now. Ok... I'll merge this and fix this later, if needed.

@agorajek agorajek merged commit 84fcde5 into main Jul 28, 2023
youngman-droid pushed a commit to youngman-droid/dj that referenced this pull request Aug 26, 2023
Rename /client to /datajunction-clients.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants