-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate title and name; name is normalized #1023
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -98,7 +98,7 @@ saveDeployment <- function(recordDir, | |
addToHistory = TRUE) { | ||
deployment <- deploymentRecord( | ||
name = deployment$name, | ||
title = deployment$title, | ||
title = application$title %||% deployment$title, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This helps make sure that a server-updated title is reflected on the client. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We may want to take this change even if we decide to abandon the other name-generation aspects of this PR. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How will automatically generating a title interact with this? Will auto-generated titles overwrite titles that have been changed on Connect? |
||
username = deployment$username, | ||
account = deployment$account, | ||
server = deployment$server, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has the side-effect of generating an
appTitle
for shinyapps.io content, which does not support title. Alternatively, we could generate a title only for Connect deployments.The other drawback of this approach is that as soon as we have generated the title, we lose track of the fact that the title was not user-specified. This means that the generated title will always overwrite the deployment record title.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may want to distinguish between "user provided title" and "generated title" when updating a discovered deployment record.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After more testing, we probably want to avoid generating titles for shinyapps.io.
The IDE deployment pane forces a normalized "title", which becomes the title and name:
After manually normalizing the title with "incredible-shiny-application" and completing this workflow, the deployment record name and title both receive the same value (as forced by the IDE).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using the CRAN version of
rsconnect::deployApp()
leaves a shinyapps.io deployment record withtitle=NULL
. The IDE deployment workflow creates deployment records with title and name both with the same value.The IDE allows mixed-case names(titles) for shinyapps.io, but mixed-case is not produced by
generateAppName()
.